mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: bjd <bjdouma@xs4all.nl>
Cc: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: kernel oops: trying to mount a corrupted xfs partition (2.6.16-rc3)
Date: Fri, 17 Feb 2006 06:31:57 +1100	[thread overview]
Message-ID: <20060217063157.B9349752@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <20060216183629.GA5672@skyscraper.unix9.prv>; from bjdouma@xs4all.nl on Thu, Feb 16, 2006 at 07:36:29PM +0100

On Thu, Feb 16, 2006 at 07:36:29PM +0100, bjd wrote:
> Trying to mount a corrupted xfs partition hanging off a Promise
> PDC20267 FastTrak100/Ukltra100 controller.
> 
> The partition contains a test Linux system that, due to an in-
> complete install, had to be halted by brute force (i.e. power off).

Any idea how/at what point it became corrupted?

> After a reboot and xfs_repair the filesystem proved to be mildly
> corrupted, but recoverable.
> 

This filesystem has not been repaired, if it had you would not
be going into log recovery when you mount it (xfs_repair clears
out the log).

> XFS mounting filesystem hda3
> Starting XFS recovery on filesystem: hda3 (logdev: internal)
> EIP:    0060:[xlog_recover_do_inode_trans+473/2688]    Tainted: P      VLI

This indicates you are running recovery - run xfs_repair first
if you know the filesystem is corrupt.

cheers.

-- 
Nathan

  reply	other threads:[~2006-02-16 19:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-16 18:36 bjd
2006-02-16 19:31 ` Nathan Scott [this message]
2006-02-17 16:54   ` Jan Engelhardt
2006-02-19 21:29     ` Nathan Scott
2006-02-19 21:52       ` Dave Jones
2006-02-20  7:09         ` Sonny Rao
2006-02-20  7:21           ` Hans Reiser
2006-02-20 16:41             ` Sonny Rao
2006-02-20 17:11               ` Sonny Rao
2006-02-21  2:04           ` Nathan Scott
2006-02-21  4:06             ` Sonny Rao

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=20060217063157.B9349752@wobbly.melbourne.sgi.com \
    --to=nathans@sgi.com \
    --cc=bjdouma@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    /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

all inboxes | Powered by JetHome®