From: "Barry Naujok" <bnaujok@melbourne.sgi.com>
To: "'Marcin Zajączkowski'" <mszpak@wp.pl>, linux-xfs@oss.sgi.com
Subject: RE: xfs_ncheck (actually xfs_db) eats a lot of memory and is killed
Date: Tue, 19 Dec 2006 10:54:49 +1100 [thread overview]
Message-ID: <200612182349.KAA23525@larry.melbourne.sgi.com> (raw)
In-Reply-To: <em5il9$tge$1@sea.gmane.org>
> -----Original Message-----
> From: xfs-bounce@oss.sgi.com [mailto:xfs-bounce@oss.sgi.com]
> On Behalf Of Marcin Zajaczkowski
> Sent: Monday, 18 December 2006 7:15 PM
> To: linux-xfs@oss.sgi.com
> Subject: Re: xfs_ncheck (actually xfs_db) eats a lot of
> memory and is killed
>
> Barry Naujok wrote:
> >> Btw, xfs_check shows two lines:
> >> link count mismatch for inode 1572882 (name ?), nlink 16,
> counted 15
> >> link count mismatch for inode 2102297 (name ?), nlink 2, counted 3
> >> Can it be reason for strange xfs_db behavior?
> >
> > No, this shouldn't be causing the xfs_db strange behaviour, but the
> > nlink count mismatch is a problem with xfs_repair 2.8.11.
> Try and use
> > xfs_repair 2.8.16 and later to fix this issue. Older versions before
> > 2.8.11 will also fix the nlink issue.
>
> I have some old system rescue CD with xfs_progs from line
> 2.7.x. Would
> it be ok?
Yes, that should be fine AFAIK.
Barry.
next prev parent reply other threads:[~2006-12-18 23:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-16 17:58 xfs_ncheck (actually xfs_db) eats a lot of memory and is killed Marcin Zajączkowski
2006-12-18 1:24 ` Barry Naujok
2006-12-18 8:15 ` Marcin Zajączkowski
2006-12-18 23:54 ` Barry Naujok [this message]
2006-12-19 7:38 ` Marcin Zajączkowski
2006-12-20 1:05 ` Barry Naujok
2006-12-21 7:42 ` Marcin Zajączkowski
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=200612182349.KAA23525@larry.melbourne.sgi.com \
--to=bnaujok@melbourne.sgi.com \
--cc=linux-xfs@oss.sgi.com \
--cc=mszpak@wp.pl \
/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