From: David Greaves <david@dgreaves.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Sylwester Gruszka <gruszex@gmail.com>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Broken XFS partition
Date: Wed, 24 Sep 2008 22:14:01 +0100 [thread overview]
Message-ID: <48DAAD99.9050904@dgreaves.com> (raw)
In-Reply-To: <20080924201745.GE24654@1wt.eu>
cc'ed xfs list
Willy Tarreau wrote:
> On Wed, Sep 24, 2008 at 12:36:25PM +0200, Sylwester Gruszka wrote:
>> Hello,
>>
>> I have a problem with XFS partition, it has broken down suddenly. I was doing
>> no special things, just browsing www and suddenly my PC has restarted, after
>> that I could not boot by PLD Th linux, after few usual kernel messages I get
>> some matrix of numbers and it stops.
First thing is why?
If you could boot then you could check the log to see if there was a disk error.
I suggest rebooting to an up-to-date rescue disk (ie 2008 vintage - mainly for
the latest xfs utils) and using smartctl -a to look at the disk state.
Then run smartctl -t long /dev/sdX or some other disk check utility.
This will take a long time to run but should let you see if there are any bad
blocks.
If so then I suggest using ddrescue to recover the disk to a spare/replacement.
Running xfs_repair on a failing disk will likely cause more trouble.
>> I realised that it is broken partition after I tried to repair system, I just
>> could not mount this partition (using sysrescuecd), 'mount' gave me lots of
>> weird numbers instead of mounting partition. It only do that way at first try,
>> the second try always freezes mount program and nothing is happening.
>>
>> Here are some screenshots (mount using SystemRescueCd-1.1.0 so the kernel is
>> propably 2.6.25.16):
>> http://img397.imageshack.us/my.php?image=dsc01043ko6.jpg
>> http://img179.imageshack.us/my.php?image=dsc01044yj4.jpg
>> http://img158.imageshack.us/my.php?image=dsc01045sr3.jpg
>> http://img221.imageshack.us/my.php?image=dsc01047js4.jpg
>>
>> PLD Linux Th booting:
>> http://img530.imageshack.us/my.php?image=dsc01048mk3.jpg
>>
>> Suse booting:
>> http://img87.imageshack.us/my.php?image=dsc01050as4.jpg
>> Except this warning it boots normal.
>>
>> Now I'm running Suse and I tried xfs_check this partition but xfs_check is
>> freezing too.
IIRC xfs_check used to be less robust than xfs_repair.
If the disk looks sound then running xfs_repair should help.
Read the manpage. no-modify (-n) may be a good idea first time.
It *may* tell you to remount to replay the log.
You should try this (mounting) but from what you've said it sounds like it won't
work.
You may then try using the -L option which will discard the log/journal. (If
you're nervous about this then wait for expert help - IMHO it's no big deal)
If this fails then you need expert help.
I have had a fair few disk failures over the years and this process is usually
quick and painless :)
David
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
next prev parent reply other threads:[~2008-09-24 21:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 10:36 Broken XFS partition Sylwester Gruszka
2008-09-24 20:17 ` Willy Tarreau
2008-09-24 21:14 ` David Greaves [this message]
2008-09-24 22:53 ` Dave Chinner
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=48DAAD99.9050904@dgreaves.com \
--to=david@dgreaves.com \
--cc=gruszex@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=w@1wt.eu \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.