> -----Original Message-----
> From: xfs-bounce@xxxxxxxxxxx [mailto:xfs-bounce@xxxxxxxxxxx]
> On Behalf Of Ferenc Wagner
> Sent: Wednesday, 13 September 2006 7:46 PM
> To: Nathan Scott
> Cc: 387057@xxxxxxxxxxxxxxx; xfs@xxxxxxxxxxx
> Subject: Re: Bug#387057: xfsprogs: repeated xfs_repair does
> not fix the filesystem
>
>
> Still, xfs_check reported:
> => link count mismatch for inode 400254 (name ?), nlink 0, counted 2
> => link count mismatch for inode 4239409 (name ?), nlink 0, counted 2
> => link count mismatch for inode 8388736 (name ?), nlink 39,
> counted 38
>
> Further runs of xfs_repair didn't bring any change. On the root
> filesystem the results are much the same, but xfs_check reports:
> => sb_ifree 3042, counted 3041
>
> I read that xfs_check is being obsoleted in the future, but not sure
> which program to trust. Are my filesystems healthy or not?
This has been reported before, can you try running an older xfsprogs before
2.8.10 and see how that goes? I think with the dir2 fixes, the nlink stuff
might be a tad broken. I'll also look into it from my end.
Barry.
|