Nathan Scott [Thu, Feb 26, 2004 at 09:34:28AM +1100]:
> > I am now using a brand new 40GB Hitachi hard disk for my notebook and
> > today I got the first problems:
> > 
> > 
> > Starting XFS recovery on filesystem: hda3 (dev: hda3)
> > Ending XFS recovery on filesystem: hda3 (dev: hda3)
> > VFS: Mounted root (xfs filesystem) readonly.
> > Mounted devfs on /dev
> > Freeing unused kernel memory: 156k freed
> > XFS mounting filesystem hda1
> > Starting XFS recovery on filesystem: hda1 (dev: hda1)
> > Ending XFS recovery on filesystem: hda1 (dev: hda1)
> > XFS mounting filesystem loop0
> > Starting XFS recovery on filesystem: loop0 (dev: loop0)
> > XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1589 of file fs/xfs/xfs_alloc.c.  Caller 0xc0198272
> > Call Trace: [<c0197151>]  [<c0198272>]  [<c0198272>]  [<c01c7fff>]  [<c01ee628>]  [<c01e5286>]  [<c01e5355>]  [<c01e6b04>]  [<c01d24fa>]  [<c01dd2cc>]  [<c01e83bd>]  [<c0203c60>]  [<c01d908f>]  [<c01f02c6>]  [<c02048e3>]  [<c02046c8>]  [<c0215517>]  [<c0185764>]  [<c015c835>]  [<c015c268>]  [<c0204890>]  [<c0204630>]  [<c015c4af>]  [<c0171ee8>]  [<c01721f4>]  [<c0172044>]  [<c01725ef>]  [<c010b34b>] 
> > Ending XFS recovery on filesystem: loop0 (dev: loop0)
> > Adding 192772k swap on /dev/discs/disc0/part2.  Priority:-1 extents:1
> > 
> > 
> > I got this after a clean shutdown. Just tell me it's an xfs error and my
> > harddisk is fine...
> 
> Filesystem recovery doesn't run after a clean shutdown...

That's what I assume(d), too.

> the "Starting/Ending XFS recovery" messages indicate that
> all of your filesystems were not unmounted by the look of
> it.

That's true and interesting, as I did a shutdown -o (poweroff) from minit, which
should have unmounted the partions. I'll retry this with -h (halt only)
this evening.

> [...] 
> So, doesn't look like a hard disk error to me, and nor does it
> look like an XFS problem.  You should be able to run xfs_repair
> on your loopback file to fix the problem.

Will reboot in half an hour, but I think as the recovery was done, it
won't have any problems anymore.

There are still some questions open for me:

1. why is it an internal xfs error?
2. why does it print a call trace?
3. how can I find out what's wrong / what should I do when seeing call
   traces? And what should I've done before (adding debugging somewhere?)

Have a nice night,

Nico

-- 
Keep it simple & stupid, use what's available.
pgp: 8D0E E27A          | Nico Schottelius
http://nerd-hosting.net | http://linux.schottelius.org