Re: another hard disk broken or xfs problems?

[Nico Schottelius <nico-kernel@schottelius.org>]

[-- Attachment #1: Type: text/plain, Size: 1624 bytes --]

Nathan Scott [Thu, Feb 26, 2004 at 02:27:41PM +1100]:
> On Thu, Feb 26, 2004 at 12:49:44AM +0100, Nico Schottelius wrote:
> > Nathan Scott [Thu, Feb 26, 2004 at 09:34:28AM +1100]:
> > > [...] 
> > > 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.
> 
> Well, recovery is a garbage-in, garbage-out process - I
> think you will need to repair that loopback file.

Well, after the recovery the system works fine again.

> > There are still some questions open for me:
> > 
> > 1. why is it an internal xfs error?
> 
> Your loopback file seems to have got corrupted, XFS reports
> this as an internal error (generic error message).

I am really wondering about the error message, as "internal errors" 
indicate for me an error in the kernel.

> > 2. why does it print a call trace?
> 
> XFS detected corruption, and tried to dump out some state info
> at the point where it noticed the problem.

I am wondering how my dmesg will look like if I've to recover some
Gigabytes of date.

And btw, do all filesystem drivers behave in this way, printing internal
errors and displaying call traces when they find errors in the
filesystem?

For me this is really confusing.

Sincerly,

Nico

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

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]