From: Eric Sandeen <sandeen@sgi.com>
To: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>
Cc: Patrick <nawtyness@gmail.com>,
linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com,
Andrew Morton <akpm@osdl.org>,
"Kristofer T. Karas" <ktk@enterprise.bidmc.harvard.edu>,
Jeff Garzik <jgarzik@pobox.com>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: Unknown Issue.
Date: Mon, 13 Dec 2004 11:50:17 -0600 [thread overview]
Message-ID: <41BDD659.9070500@sgi.com> (raw)
In-Reply-To: <2E314DE03538984BA5634F12115B3A4E01BC4179@email1.mitretek.org>
Piszcz, Justin Michael wrote:
> Ah, good question, yes I used xfs_repair, at this point I knew I had to
> restore from backup and answered "y" to all questions. I am not sure
> but I do not recall the log being dirty.
Hm, xfs_repair does not ask any questions.
> In the logs on my main machine, it showed the following when it
> attempted to mount the two filesystems (root and boot, /dev/hde4 and
> /dev/hde1 respectively).
> Dec 5 08:23:53 jpiszcz kernel: XFS internal error
> XFS_WANT_CORRUPTED_GOTO at line 1583 of file fs/xfs/xfs_alloc.c. Caller
> 0xc021de57
(having trouble replaying the log here)
Ok, so XVM has found something wrong at this point. Any chance the box
had a power failure? Write caches on ide drives can wreak havoc with
journaling filesystems... i.e. what happened between "the filesystem
was working" and "i remounted the filesystem and got this"
>
> As far as bad disk/memory, I have tested both systems with memtest86 and
> the result was 0 errors, as far as the disks go, I have not experienced
> any problems with either of them until I moved to 2.6.9/2.6.10-rc{1,2}.
ok
-Eric
next prev parent reply other threads:[~2004-12-13 17:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 17:14 Unknown Issue Piszcz, Justin Michael
2004-12-13 17:17 ` Patrick
2004-12-13 17:50 ` Eric Sandeen [this message]
2004-12-13 17:56 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2005-01-06 13:33 hard__ware
2004-12-13 18:57 Piszcz, Justin Michael
2004-12-13 17:20 Piszcz, Justin Michael
2004-12-13 17:27 ` Patrick
2004-12-13 13:57 Piszcz, Justin Michael
2004-12-13 17:04 ` Eric Sandeen
2004-12-13 17:13 ` Patrick
2004-12-12 21:14 Patrick
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=41BDD659.9070500@sgi.com \
--to=sandeen@sgi.com \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=justin.piszcz@mitretek.org \
--cc=ktk@enterprise.bidmc.harvard.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=nawtyness@gmail.com \
--cc=torvalds@osdl.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