On Wed, 2007-08-29 at 21:34 +0100, Peter Grandi wrote: > >>> On Wed, 29 Aug 2007 14:39:31 -0400, "Justin Bronder" > >>> <[EMAIL PROTECTED]> said: > > [ ... using 'nointegrity' to disable journaling ... ] > > jsbronder> a.) Mount the filesystem with nointegrity and leave > jsbronder> it like that. If the file has been opened, written > jsbronder> to, and closed, do we stand to lose anything should a > jsbronder> power loss happen later? > > I have seen the reply by DavidK, and let me add that this > question is a bit fuzzy as for example in "lose anything".
I agree with everything you said here. Let me summarize the difference between "integrity" (default behavior), and "nointegrity". With "integrity", you may lose recent un-committed changes to files, including unsync'ed file data, but everything previously sync'ed to disk should be okay, and the file system metadata will be in a consistent state. With "nointegrity", you could lose anything, including previously sync'ed data. It will be necessary for fsck to do a full recovery, which won't necessarily recover damaged files and directories. -- David Kleikamp IBM Linux Technology Center ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
