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 09:34:28 +1100 [thread overview]
Message-ID: <20040225223428.GD640@frodo> (raw)
In-Reply-To: <20040225220051.GA187@schottelius.org>
On Wed, Feb 25, 2004 at 11:00:51PM +0100, Nico Schottelius wrote:
> Hello!
>
> 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...
the "Starting/Ending XFS recovery" messages indicate that
all of your filesystems were not unmounted by the look of
it.
Probably file data for the file backing your loopback device
has been lost/corrupted due to what looks like an "abrupt" end
before reboot (only metadata is journalled), and hence trying
to recover the loop device is going horribly wrong.
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.
cheers.
--
Nathan
next prev parent reply other threads:[~2004-02-25 22:39 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 [this message]
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
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=20040225223428.GD640@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