On 8/29/07, Peter Grandi <[EMAIL PROTECTED]> 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". >
Thanks to both of you for your quick replies. I'll just clarify here what I was asking, because I believe you have both already answered my questions. By "lose anything" I meant to suggest that assuming the data has been written to disk, will JFS have any problems later on. I'm not overly worried about the metadata for, as mentioned, the filesystem only gets one large file at a time, which is then moved off later. As David mentioned, the filesystem is used only for these files, and while not desired, the data can be recovered. So if I'm getting a performance increase, and my only worry is a power loss before the data exists on the hard drive, then I'm pretty happy using nointegrity. Thanks again, Justin. ------------------------------------------------------------------------- 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
