Messages in this thread | | | Date | Fri, 9 May 2003 18:39:28 -0400 | From | Joe Korty <> | Subject | Re: ext3/lilo/2.5.6[89] (was: [KEXEC][2.5.69] kexec for 2.5.69available) |
| |
> One suggestion: ext3 is a journalled version of ext2, so if you can > boot with whatever is needed to specify that the boot partition is > to be mounted as ext2 rather than ext3, you can isolate the journal > system: If the problem's still there in ext2 then the journal is > not involved, but if the problem vanishes there, it's something to > do with the journal. > > I have to admit that the above sounds very much like the details > are being recorded in the journal, but the journal isn't being > played back to update the actual files.
I recall reading on lkml once that an ext3 sync(2) merely pushes volatile data/metadata out to the journal rather than to to files themselves.
Joe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |