All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: "Daniele P." <daniele@interline.it>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_ncheck gives outdated and partial result
Date: Fri, 20 Oct 2006 12:16:35 -0500	[thread overview]
Message-ID: <45390473.3080904@sandeen.net> (raw)
In-Reply-To: <200610200858.08718.daniele@interline.it>

Daniele P. wrote:
> Hi All,
> I'm here to ask a couple of question regarding xfs_ncheck.
> I'm using xfs_db version 2.6.20
> 
> The first question is:
> Is it right that I have to unmount/mount the filesystem before
> using it (1), or to get the partial right (3) answer?
> And why it's print only the first file name for inodes pointed
> by multiple files (2)?

I think Lachlan had good answers to your questions... I'm curious, are
you using xfs_ncheck on a mounted filesystem for any particular reason?
 It seems that maybe if you are concerned about the out-of-date info on
a mounted filesystem, maybe you are attempting to use this from a script
or something as part of a larger tool, and that may not be a good idea
in general.  xfs_ncheck, a wrapper around xfs_db, reads the block device
directly, and nothing in the kernel guarantees consistency between the
block device address space and the filesystem address space.

-Eric

  parent reply	other threads:[~2006-10-20 17:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-20  6:58 xfs_ncheck gives outdated and partial result Daniele P.
2006-10-20 11:35 ` Lachlan McIlroy
2006-10-20 17:16 ` Eric Sandeen [this message]
2006-10-23  4:26 ` Timothy Shimmin

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=45390473.3080904@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=daniele@interline.it \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.