From: "Barry Naujok" <bnaujok@melbourne.sgi.com>
To: 'Ferenc Wagner' <wferi@niif.hu>
Cc: xfs@oss.sgi.com
Subject: RE: Bug#387057: xfsprogs: repeated xfs_repair does not fix the filesystem
Date: Thu, 14 Sep 2006 12:03:28 +1000 [thread overview]
Message-ID: <200609140157.LAA22186@larry.melbourne.sgi.com> (raw)
In-Reply-To: <87zmd4jdzz.fsf@tac.ki.iif.hu>
> -----Original Message-----
> From: xfs-bounce@oss.sgi.com [mailto:xfs-bounce@oss.sgi.com]
> On Behalf Of Ferenc Wagner
> Sent: Wednesday, 13 September 2006 7:46 PM
> To: Nathan Scott
> Cc: 387057@bugs.debian.org; xfs@oss.sgi.com
> 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.
next prev parent reply other threads:[~2006-09-15 2:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060911223008.5160.98142.reportbug@szonett.ki.iif.hu>
[not found] ` <20060912085025.A3552962@wobbly.melbourne.sgi.com>
2006-09-13 9:46 ` Bug#387057: xfsprogs: repeated xfs_repair does not fix the filesystem Ferenc Wagner
2006-09-14 2:03 ` Barry Naujok [this message]
2006-09-15 3:10 ` Peter Palfrader
2006-09-15 11:41 ` Ferenc Wagner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200609140157.LAA22186@larry.melbourne.sgi.com \
--to=bnaujok@melbourne.sgi.com \
--cc=wferi@niif.hu \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox