On Thu, Oct 03, 2002 at 08:35:41PM -0500, Eric Sandeen wrote:
> Odd. Just to make sure I read everything right - xfs itself was
> hanging in recovery, and your oopses came from when you tried to sync
> with SysRq?
Two cases.
Case 1: if system panicked (like the panics I sent ksymoops'd oopses
of), Alt+SysRq+S will sync all discs until my 00:0a (/dev/sda10,
/opt/data) and then send another panic (I also sent ksymoops'd oopses of
this).
Case 2: on bootup from an unclean shutdown, XFS hangs on mount recovery
of /opt/data (/dev/sda10). While it's here, an attempt to sync will
again get stuck at 00:0a, but without a panic, it will just stop.
> And then it sounds like the only thing you did before the mount was
> ultimately successful, was to run xfs_check... which should be a
> read-only test, and should not have changed anything about the fs, as
> far as I know.
I booted using "init=/bin/sh" to bypass automounting, ran xfs_check on
/dev/sda10 just to check -- like you I knew this was read-only and
didn't expect it to change anything -- and then attempted to mount,
which worked, and well... reboot after a clean unmount (and another
xfs_check just to make sure).
> I think the most helpful thing (in retrospect) would have been to
> break into kdb, and see where mount was stuck during recovery.
Ack. This system does not have kdb support built into it. :(
> I'm not sure what to make of this problem...
I wonder if backing up my data for this partition, doing another
mkfs.xfs, and then restoring my data will help. Thoughts?
Thanks everyone for your time.
--> Jijo
--
Federico Sevilla III : http://jijo.free.net.ph
Network Administrator : The Leather Collection, Inc.
GnuPG Key ID : 0x93B746BE
|