Yes. Files that they accessed in a read-only fashion, and untouched
files, seem entirely unharmed.
> Question on the table is: did the kernel write the wrong
> stuff into those files, or did it forget to write the
> right stuff?
> Is the incorrect content within those files recognisable
> at all? If so, what is it?
Yes. There are three things that I noted as incorrect in the files.
Many of them, but not all, featured large blocks of NULL (0) bytes, on
the order of 2K worth of them. No exacting counts available but they did
fill a page in an 80x30 terminal, generally.
Several of the files featured the "right" content, just in the wrong
location. For example, the galeon 'bookmarks.xbel' file started about a
third of the way into it's correct content.
Only one of the files seemed to be gratuitously truncated, the mozilla
The remaining file content seemed to be randomly swizzled. I found part
of a .overview file in .newsrc.eld, for example, and part of the
.newsrc.eld elsewhere. Also, 'active' got written to a mail folder...
There were *no* cases where the file content was unrecognizable with the
exception of the NULL bytes. In *every* case the content was from a
*completely* different file.
This included files in different directories getting content swapped, so
a file in ~ got content from ~/Mail/<group>/, so it's not just within
the same directory.
I can't think of a single verifiable case where a file got the wrong
data from another process, though. That's not a "didn't", just a "can't
remember seeing", though, so don't take that as gospel.
>> I also found corruption in the mozilla prefs.js file from the same
>> application. That was simply a truncated file -- no NULL bytes or
>> anything, just a file that cut off half way through a single
>> expression like:
>> This /may/ be the logical break between two write(2) calls or a
>> partly completed write, though.
> That sounds like metadata corruption. Are you sure that the file
> doesn't have a chunk of invisible nulls in it, after the text?
Yes. I used an editor that displays the NULL byte correctly in files to
view it when looking for damage and there was *no* NULL content in this
None of the NULL bytes were at the end of the file, always in the
middle of the data.
> Because if it got chopped off in this manner, e2fsck should have
> detected something.
Yup. I carefully watched the forced fsck and no errors. This is:
] fsck.ext3 -V
e2fsck 1.27 (8-Mar-2002)
Using EXT2FS Library version 1.27, 8-Mar-2002
>> > And no, it doesn't promise anything good - last time we had crap in
>> > truncate/mmap interaction it was a hell to fix.
>> > I suspect that you had screwed the truncate exclusion warranties
>> > up. If _any_ IO happens in the area currently manipulated by
>> > ->truncate() - you are screwed and results would look pretty much
>> > like the things mentioned in bug report.
>> Ick. Er, good luck. I am quite happy to provide more information and
>> even to install a scratch disk and try to get it to fail the same way
>> if you wish.
> It would be good if you had the time to do that.
Sure. I will have a run at reproducing it in an hour or two, then post
the results to the list under this thread, with a direct CC. :)
-- Nobody objects to a woman being a good writer or sculptor or geneticist if at the same time she manages to be a good wife, good mother, good-looking, well-groomed and unaggressive. -- Leslie M. McIntyre - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/