On Fri, 2007-08-24 at 08:10 -0700, [EMAIL PROTECTED] wrote: > Quoting Jim Crilly <[EMAIL PROTECTED]>: > > >> I tested the exact same thing again but waited 60 seconds after saving > >> the file, and then yanked the power out. Upon a boot up, the file was > >> intact and the save worked. So you still have about a 60 second window > >> of newly written files and a power loss for data corruption, unless > >> the program can sync it to disk before that. > >> > > > > Well I'm only passing on what the XFS devs have said, all of my boxes are > > on UPSes so I rarely saw the issue anyway. But are you sure the squares you > > saw in the word doc were nulls? The FAQ page says that you can use the > > xfs_bmap command to see if it has any extents allocated and if it does then > > it would likely be another issue. > > > > I'm not sure. > I'm thinking the nulls thing is indeed fixed, but perhaps its still > something different than the very nature of XFS. My understanding is > limited of its mechanics, but since XFS will never journal data, only > meta-data, then won't there always be the chance that a file can get > corrupted on a timely power loss? > > UPS is a good buddy of mine too. :)
I'd trust XFS with my data, but we have an expensive support contract with SGI, and it's sub-optimal to use their volume management tool (XVM) without XFS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
