From: Nathan Scott <nathans@sgi.com>
To: Nico Schottelius <nico-kernel@schottelius.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: another hard disk broken or xfs problems?
Date: Thu, 26 Feb 2004 14:27:41 +1100 [thread overview]
Message-ID: <20040226032741.GB1177@frodo> (raw)
In-Reply-To: <20040225234944.GD187@schottelius.org>
hi there,
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.
> 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).
> 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.
> 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?)
xfs_repair will tell you whats wrong, and should fix it.
cheers.
--
Nathan
next prev parent reply other threads:[~2004-02-26 3:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 22:00 another hard disk broken or xfs problems? Nico Schottelius
2004-02-25 22:34 ` Nathan Scott
2004-02-25 23:10 ` Michael Joy
2004-02-28 21:43 ` Stephen Satchell
2004-02-29 8:07 ` John Bradford
2004-02-25 23:49 ` Nico Schottelius
2004-02-26 3:27 ` Nathan Scott [this message]
2004-02-26 8:25 ` Nico Schottelius
2004-02-26 9:46 ` Nathan Scott
2004-02-26 19:26 ` Mike Fedyk
2004-02-27 5:53 ` Nathan Scott
2004-02-26 10:02 ` Rogier Wolff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040226032741.GB1177@frodo \
--to=nathans@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nico-kernel@schottelius.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox