Date: Mon, 25 Aug 2008 12:02:39 +1000
From: Dave Chinner <david@fromorbit.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: xfs@oss.sgi.com
Subject: Re: agi unlinked bucket
Message-ID: <20080825020239.GQ5706@disturbed>
Mail-Followup-To: Christian Kujau <lists@nerdbynature.de>,
	xfs@oss.sgi.com
References: <alpine.DEB.1.10.0808230017150.20126@sheep.housecafe.de> <alpine.DEB.1.10.0808231412230.20126@sheep.housecafe.de> <20080825003929.GN5706@disturbed> <alpine.DEB.1.10.0808250254380.26780@sheep.housecafe.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.1.10.0808250254380.26780@sheep.housecafe.de>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: xfs-bounce@oss.sgi.com
Errors-to: xfs-bounce@oss.sgi.com
Precedence: bulk

On Mon, Aug 25, 2008 at 03:05:24AM +0200, Christian Kujau wrote:
> On Mon, 25 Aug 2008, Dave Chinner wrote:
>> If you do a mount then unmount then rerun xfs-check, does it go
>> away?
>
> Did that a few times already, and the fs is getting mounted during boot  
> anyway, but xfs_check still complains:

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.

> --------------------------------------
> # xfs_check /dev/mapper/md3 2>&1 | tee fsck_md3.log
> agi unlinked bucket 26 is 20208090 in ag 0 (inode=20208090)
> link count mismatch for inode 128 (name ?), nlink 335, counted 336
> link count mismatch for inode 20208090 (name ?), nlink 0, counted 1
> # mount /mnt/md3
> # dmesg | tail -2
>  XFS mounting filesystem dm-3
>  Ending clean XFS mount for filesystem: dm-3
> # grep xfs /proc/mounts
> /dev/mapper/md3 /mnt/md3 xfs ro,nosuid,nodev,noexec,nobarrier,noquota 0 0

You are not using barriers. Are you using write caching? The
problems with filesystem corruption on powerloss when using volatile
write caching have traditionally shown up in directory
corruptions...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com