Messages in this thread | | | Date | Wed, 14 Jul 2004 09:57:23 -0700 | From | Roy Butler <> | Subject | Re: kconfig's file handling |
| |
Chris,
Chris Wedgwood wrote: > On Tue, Jul 13, 2004 at 11:27:50PM -0700, Roy Butler wrote: > > >>By example, if you create a file, write to it, and then delete it >>fast enough, it will never hit the disk under XFS. > > > Nor will it under some other filesystems... and in the above scenario > I'm not sure that matters, why must a temporary file hit the disk at > all? > > > --cw >
Suppose you want to do something with the file's contents before you delete it, but the system goes down before you have the chance. Wasn't that the impetus for this thread? With XFS, the potential for data loss is greater; that was my point. I believe that everyone who pays extra for batter-backed I/O caches would agree. :) Sure, different filesystems have their options, but this liability is ingrained in XFS.
Roy - 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/
| |