From: "Daniele P." <daniele@interline.it>
To: xfs@oss.sgi.com
Subject: xfs_ncheck gives outdated and partial result
Date: Fri, 20 Oct 2006 08:58:08 +0200 [thread overview]
Message-ID: <200610200858.08718.daniele@interline.it> (raw)
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)?
(1)
# mkfs.xfs /dev/hda5
meta-data=/dev/hda5 isize=256 agcount=16, agsize=152617 blks
= sectsz=512
data = bsize=4096 blocks=2441872, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=1
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=2560, version=1
= sectsz=512 sunit=0 blks
realtime =none extsz=65536 blocks=0, rtextents=0
# mount /dev/hda5 /mnt/hda5/
# touch /mnt/hda5/a
# xfs_ncheck -i 131 /dev/hda5
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed. Mount the filesystem to replay the log, and unmount it before
re-running xfs_ncheck. If you are unable to mount the filesystem, then use
the xfs_repair -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this.
must run blockget -n first
(2)
# ln /mnt/hda5/a /mnt/hda5/b
# ls -i /mnt/hda5/
131 a 131 b
# umount /mnt/hda5
# mount /dev/hda5 /mnt/hda5
# xfs_ncheck -i 131 /dev/hda5
131 a
(3)
# ln /mnt/hda5/a /mnt/hda5/c
# xfs_ncheck -i 131 /dev/hda5
131 a
# rm /mnt/hda5/a
# xfs_ncheck -i 131 /dev/hda5
131 a
# umount /mnt/hda5
# mount /dev/hda5 /mnt/hda5
# xfs_ncheck -i 131 /dev/hda5
131 b
Thanks in advance,
Daniele P.
next reply other threads:[~2006-10-20 8:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 6:58 Daniele P. [this message]
2006-10-20 11:35 ` xfs_ncheck gives outdated and partial result Lachlan McIlroy
2006-10-20 17:16 ` Eric Sandeen
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=200610200858.08718.daniele@interline.it \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox