Re: Fwd: panic(9) vs. RB_NOSYNC
Matthew Dillon <[email protected]>
| Newsgroups | gmane.os.dragonfly-bsd.kernel |
|---|---|
| Message-ID | <[email protected]> |
:Thanks. At least I read code's intention right. :)
:
:> Most modern filesystems don't corrupt any more if left unsynchronized,
:> but the real problem here is that filesystem do so much caching in
:> memory, particularly when files are mmap()'d RW, that not at least
:> trying to sync can result in disarray (rather than corruption) on boot
:
:Do you mean that "corruption" == "file metadata corruption" and "disarray" ==
:"file data-only corruption"?
No filesystem that I know of guarantees operational order inbetween
fsyncs, particularly if files are mmap()'d shared/RW.
-Matt
Matthew Dillon
<[email protected]>