From: xiaowei hu <xiaowei.hu@oracle.com>
To: xfs@oss.sgi.com
Cc: wen.gang.wang@oracle.com
Subject: segment fault when running xfs_check -s
Date: Mon, 21 Jun 2010 10:55:18 +0800 [thread overview]
Message-ID: <1277088918.20616.81.camel@redfuture-desktop> (raw)
Hi,
Recently I was playing with xfsprogs, and did some test on xfs_check
tools in this mothod:
1.make a xfs fs on one partition.
mkfs.xfs -f /dev/sda2
2.randomly modify some blocks on this volume using xfs_db.
xfs_db -x -c blockget -c "blocktrash -3 -s 36 -n 81" /dev/sda2
3.run xfs_check -s
xfs_check -s /dev/sda2
the output saying:
[root@test1 ~]# xfs_check -s /dev/sda2
bad version number 0x78 for inode 135
bad magic number 0xa855 for inode 154
bad magic number 0x5024 for inode 165
/usr/local/bin/xfs_check: line 28: 769 Segmentation fault xfs_db
$DBOPTS -F -i -p xfs_check -c "blockget$OPTS" $1
if I run xfs_check without -s option, don't have this fault.
Is this a known problem?
I tried the latest code ,also have this problem.
thanks,
Xiaowei
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-06-21 2:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 2:55 xiaowei hu [this message]
2010-06-21 5:38 ` segment fault when running xfs_check -s Dave Chinner
2010-06-22 7:17 ` xiaowei hu
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=1277088918.20616.81.camel@redfuture-desktop \
--to=xiaowei.hu@oracle.com \
--cc=wen.gang.wang@oracle.com \
--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