From: Dave Chinner <david@fromorbit.com>
To: Kirk Anderson <kirkande@tx.rr.com>
Cc: xfs@oss.sgi.com
Subject: Re: Buffalo LS-Q4.0 Raid 5 XFS errors
Date: Fri, 30 Mar 2012 10:03:17 +1100 [thread overview]
Message-ID: <20120329230317.GD18323@dastard> (raw)
In-Reply-To: <005101cd0df9$67f61250$37e236f0$@tx.rr.com>
On Thu, Mar 29, 2012 at 05:15:08PM -0500, Kirk Anderson wrote:
> Thank you again for your help. Please let me know what my next step should
> be.
>
> Here is the output from the dd command. My understanding is that I use the
> /dev/sd[a-d]6 for mine as the cat /proc/mdstat indicated that
> md2 : active raid5 sda6[0] sdd6[3] sdc6[2] sdb6[1]
> 2906278656 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
>
> root@LS-QLF55:~# dd if=/dev/sda6 bs=512 count=1 2> /dev/null | hexdump -C
> 00000000 58 46 53 42 00 00 10 00 00 00 00 00 2b 4e 92 c0 |XFSB........+N..|
.....
Ok, so that's a superblock. Does it match the output of
# dd if=/dev/md2 bs=512 count=1 2> /dev/null | hexdump -C
It should match according to the above, but it doesn't hurt to
confirm. If it doesn't then your RAID device has been SBTW and
that's what you need to fix first.
If it does match, can you dump the output of
# dd if=/dev/md2 bs=512 count=4 2> /dev/null | hexdump -C
and
# xfs_db -c "sb 0" -c p -c "agf 0" -c p -c "agi 0" -c p /dev/md2
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:[~2012-03-29 23:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 0:06 Buffalo LS-Q4.0 Raid 5 XFS errors Kirk Anderson
2012-03-29 6:40 ` Dave Chinner
[not found] ` <002501cd0dbe$24be21c0$6e3a6540$@tx.rr.com>
2012-03-29 21:31 ` Dave Chinner
2012-03-29 22:15 ` Kirk Anderson
2012-03-29 23:03 ` Dave Chinner [this message]
2012-03-29 23:29 ` Kirk Anderson
2012-03-29 23:52 ` Dave Chinner
[not found] ` <005601cd0e11$c0b62d90$422288b0$@tx.rr.com>
2012-03-30 4:46 ` Eric Sandeen
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=20120329230317.GD18323@dastard \
--to=david@fromorbit.com \
--cc=kirkande@tx.rr.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox