28 Apr
2007
28 Apr
'07
10:13 p.m.
On Saturday 28 April 2007, Jean-Jacques MOURIS wrote:
Hello,
I have a strange situation with some files (photos from digital camera):
Although the timestamp of the file is not altered, the content of the
file is not displayable anymore in any viewer. Looking at the content of
the files (hexdump) told me that all of these files only consist of NULL
bytes. There are 42 files corrupted, including one mpg file of 216 MB
I tried to investigate further what could have happened to those files.
Unfortunately, I have no idea when some event could have happened which
might cause the file content to be nulled, but I am sure they have been
intact only a couple of days before.
I tried to investigate with the command debugreiserfs -D /dev/hdb3 . In
the resulting file I found the filename and inodes of the corrupted
files with entries like shown below. These entries do not differ from
those I can find for uncorrupted files.
Is there anybody out there who has some idea
- why suddenly files can be corrupted this way
- where I possibly can find more information about what happened (maybe
logfiles to analyse, look for what???)
- if these files might be recovered, and how
In earlier days, when I used Reiserfs in Suse, I also had the strangiest
effects with this fs when the disc becomes full. I found out, that this FS
doesn't report, when it cannot save a file entirely. The system becomes
unstable, because of corrupted files and it doesn't report.
Perhaps. this might be useful to you.
I use now ext3 since I switched to kubuntu and have no such problems at all.
Al