On Fri, Aug 08, 2003 at 09:05:06AM -0500, Steve Lord wrote:
> On Fri, 2003-08-08 at 00:18, djoneill@xxxxxxx wrote:
>
> > ustat(0x304, 0xbfffe724
> >
>
> The fact that you are hanging in ustat is strange, is this after the
> failed mount oops (i.e. without a reboot)? It is possible that the
> mount failure left the device locked and you will need a reboot to
> clear it up.
>
> Try a reboot, then do xfs_logprint -t /dev/hda4 and send us the output,
> You can try the mount again and see if the oops repeats, if it does
> reboot one more time, and run xfs_repair -L (to ignore the log). If the
> ustat hang is there after a reboot then you may have hardware issues.
>
I commented out the fstab entry for the filesystem, then ran xfs_repair
which now does not hang and gives the following output:
think# xfs_repair /dev/hda4
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
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_repair. If you are unable to mount the filesystem, then
use
the -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.
I ran xfs_logprint and the output is extremely long. I have attached it
rather than include it here.
xfs.logprint
Description: Text document
|