|To:||Dave Chinner <david@xxxxxxxxxxxxx>|
|Subject:||Re: agi unlinked bucket|
|From:||Christian Kujau <lists@xxxxxxxxxxxxxxx>|
|Date:||Mon, 25 Aug 2008 13:53:54 +0200 (CEST)|
|References:||<alpine.DEB.1.10.0808230017150.20126@xxxxxxxxxxxxxxxxxx> <alpine.DEB.1.10.0808231412230.20126@xxxxxxxxxxxxxxxxxx> <20080825003929.GN5706@disturbed> <alpine.DEB.1.10.0808250254380.26780@xxxxxxxxxxxxxxxxxx> <20080825020239.GQ5706@disturbed>|
|User-agent:||Alpine 1.10 (DEB 962 2008-03-14)|
On Mon, 25 Aug 2008, Dave Chinner wrote:
Ok, so if you do a 'ls -i /' do you see an inode numbered 20208090? i.e. is it the unlinked bucket that is incorrect, or the root directory.
I see inode 128 (the mountpoint), but I don't see inode 20208090 (I've used find).
You are not using barriers.
I think, I can't, as I am using XFS on top of dm-crypt. And barriers are not supported for dm, right?
Are you using write caching?
Just check with hdparm on the underlying hdb...yes, write caching is active.
The problems with filesystem corruption on powerloss when using volatile write caching have traditionally shown up in directorycorruptions...
Hm, I see. Still strange, that it does not complain during mount(8). But I guess things like these are just not checked during mount.
Thanks, Christian. -- BOFH excuse #57: Groundskeepers stole the root password
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||your website, Walter Morris|
|Next by Date:||Re: XFS vs Elevators (was Re: [PATCH RFC] nilfs2: continuous snapshotting file system), Jamie Lokier|
|Previous by Thread:||Re: agi unlinked bucket, Dave Chinner|
|Next by Thread:||Re: agi unlinked bucket, Timothy Shimmin|
|Indexes:||[Date] [Thread] [Top] [All Lists]|