xfs
[Top] [All Lists]

Re: XFS corruption during power-blackout

To: linux-xfs@xxxxxxxxxxx
Subject: Re: XFS corruption during power-blackout
From: Ethan Benson <erbenson@xxxxxxxxxx>
Date: Wed, 6 Jul 2005 20:36:35 -0800
In-reply-to: <20050707034417.GC1070@frodo>
Mail-copies-to: nobody
Mail-followup-to: linux-xfs@xxxxxxxxxxx
References: <20050705181057.GA16422@xxxxxxxxxxxxxxxxxx> <200507060424.HAA27591@xxxxxxxxxxxxx> <20050706112719.GA18969@xxxxxxxxxx> <20050707025607.GJ25980@xxxxxxxxxxxxxxx> <20050707034417.GC1070@frodo>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.3.28i
On Thu, Jul 07, 2005 at 01:44:18PM +1000, Nathan Scott wrote:
> Hi Ethan,
> 
> On Wed, Jul 06, 2005 at 06:56:07PM -0800, Ethan Benson wrote:
> > I believe this is the same behavior as ext2, newer versions of ext2
> > also had a different sync flag specifically for directories to ensure
> > directory updates are synchronous, this one is not yet supported by XFS
> > (at least that I am aware).  I think this flag is 2.6 only as well.
> 
> I added support for the mount option (dirsync), but I never got
> around to making it an inode flag too.. (got a patch for me? :)

hmm, not at the moment. I didn't know we got the dirsync stuff, but I
haven't been paying too close attention lately.

the attr should't be that difficult to add, mainly depends how much
granularity is currently allowed in your dirsync code.  +S is easy
since it basically just forces O_SYNC flags on all open() calls, can
this work the same?

also is dirsync 2.6 only? or am I thinking of something else.

-- 
Ethan Benson
http://www.alaska.net/~erbenson/

Attachment: pgpJ7Zi8gIPY4.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>