From: Dave Chinner <david@fromorbit.com>
To: pbrunnen <PBrunnen@bccnetworks.net>
Cc: xfs@oss.sgi.com
Subject: Re: XFS Filesystem not mounting
Date: Tue, 14 Sep 2010 11:21:51 +1000 [thread overview]
Message-ID: <20100914012151.GF411@dastard> (raw)
In-Reply-To: <29704010.post@talk.nabble.com>
On Mon, Sep 13, 2010 at 04:45:23PM -0700, pbrunnen wrote:
>
> Hello all,
>
> Pardon the cross post...
>
> I have an XFS filesystem (not my root filesystem) on an OpenSuSE system that
> is not mounting.
What kernel version is that?
> We had a power failure over the weekend. All but one of our XFS mounts is
> comming up. Its a large mount (2TB) and I am not seeing errors per se...
What sort of hardware is it on? (raid controller, raid level, etc)
> But after attempting to mount it, it has been 4 hours and all we see in
> either dmesg output or in the messages file from the kernel is:
>
> "Starting FXS recovery on filesystem: sdd1 (logdev: internal)"
>
> Our mount process is dead and I don't see any disk i/o going on. Am I
> missing something here on this?
There's a good chance your storage is in a bad state. Can you send the output
of "echo w > /proc/sysrq-trigger" when the system is hung?
> I rebooted the box once earlier and was able mount read-only with
> norecovery...
>
> I tried xfs_check and it also produced a dead "xfs_df -i -p xfs_check -c
> check /dev/sdd1"
Definitely sounding like a hardware issue - once again can you post
the output of the above sysrq command when it is hung there?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-14 1:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 23:45 XFS Filesystem not mounting pbrunnen
2010-09-14 1:21 ` Dave Chinner [this message]
2010-09-14 4:29 ` pbrunnen
2010-09-14 5:40 ` Michael Monnerie
2010-09-14 6:25 ` Emmanuel Florac
2010-09-14 12:32 ` pbrunnen
2010-09-14 14:03 ` Michael Monnerie
2010-09-14 16:09 ` Stan Hoeppner
2010-09-14 16:35 ` pbrunnen
2010-09-14 18:03 ` Now: Debian issues, WAS: " Stan Hoeppner
2010-09-14 20:32 ` Emmanuel Florac
2010-09-15 1:07 ` pbrunnen
2010-09-15 3:51 ` Stan Hoeppner
2010-09-15 13:15 ` pbrunnen
2010-09-15 0:44 ` Dave Chinner
2010-09-15 2:54 ` Stan Hoeppner
2010-09-15 0:49 ` pbrunnen
2010-09-14 16:25 ` pbrunnen
2010-09-14 4:43 ` pbrunnen
2010-09-14 5:40 ` 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=20100914012151.GF411@dastard \
--to=david@fromorbit.com \
--cc=PBrunnen@bccnetworks.net \
--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.