View Incident:
http://co-op.engr.sgi.com/BugWorks/code/bwxquery.cgi?search=Search&wlong=1&view_type=Bug&wi=801764
Status : open Priority : 4
*Assigned Engineer : nathans Submitter : dxm
Project : xfs-linux Assigned Group : xfs-linux
Opened Date : 09/13/00 *Modified User : nathans
*Modified User Domain : engr *Description :
both "xfs_check" and "xfs_repair -n" may be run on a mounted
filesystem and will usually produce lots of warnings about
filesystem corruption due to the inconsistent state the FS
is in.
Both tools should fail or at least warn that the FS is mounted
before proceeding.
xfs_logprint should also warn when run on a mounted FS, but
can still be useful when mounted.
.....
==========================
ADDITIONAL INFORMATION (REASSIGN)
From: nathans@engr (BugWorks)
Date: Sep 14 2000 07:05:49PM
==========================
hi,
I have a (trivial) fix which does this:
$ logprint/xfs_logprint /dev/hda5
xfs_logprint: /dev/hda5 contains a mounted filesystem
...[carries on]...
$ sh db/xfs_check.sh /dev/hda5
xfs_check: /dev/hda5 contains a mounted filesystem
fatal error -- couldn't initialize XFS library
[exit]
$ sudo repair/xfs_repair -n /dev/hda6
xfs_repair: /dev/hda6 contains a mounted filesystem
fatal error -- couldn't initialize XFS library
[exit]
for the folks cloning the tree - is this a beta candidate,
or shall I wait and check in the change later?
many thanks.
|