| To: | Steve Lord <lord@xxxxxxx> |
|---|---|
| Subject: | Re: trying to repair/recover xfs filesystem after system crash |
| From: | daniel <djoneill@xxxxxxx> |
| Date: | Fri, 8 Aug 2003 14:50:58 -0500 |
| Cc: | Nathan Scott <nathans@xxxxxxx>, onedj@xxxxxxx, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <1060351505.9279.6.camel@jen.americas.sgi.com> |
| References: | <25353.1060311459@www61.gmx.net> <20030808031433.GC1124@frodo> <20030808051806.GA1052@think.internal.alaya.net> <1060351505.9279.6.camel@jen.americas.sgi.com> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.4i |
So has Steve Lord on 09:05 Friday 08 August 2003 written: > 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. The problem had to be what you mentioned: the mount failure at boot was locking the device. Turning off auto mounting at boot and running xfs_repair -L /dev/hda4 solved the problem. -- Daniel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: trying to repair/recover xfs filesystem after system crash, djoneill |
|---|---|
| Next by Date: | CVS repository not working?, Bernhard Erdmann |
| Previous by Thread: | Re: trying to repair/recover xfs filesystem after system crash, djoneill |
| Next by Thread: | TAKE - acl, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |