From: Eric Sandeen <sandeen@sandeen.net>
To: Harry Mangalam <harry.mangalam@uci.edu>
Cc: xfs@oss.sgi.com
Subject: Re: XFS on ARM-based Linux on USR8700 NAS appliance w/ mdadm/RAID5
Date: Mon, 23 Feb 2009 15:31:42 -0600 [thread overview]
Message-ID: <49A315BE.7090607@sandeen.net> (raw)
In-Reply-To: <200902231320.05320.harry.mangalam@uci.edu>
Harry Mangalam wrote:
> Thanks for the quick response Eric!
>
> On Monday 23 February 2009, Eric Sandeen wrote:
>> Harry Mangalam wrote:
>>> Here's an unusual (long) tale of woe.
>>>
>>> We had a USRobotics 8700 NAS appliance with 4 SATA disks in
>>> RAID5:
>
> <snip>
>
>> However this wouldn't cause a superblock mis-read like this. If
>> you get it mounted, you *may* run into what looks like directory
>> corruption on the PC, though, due to the alignment issue.
>>
>> Anyway, first, I'd look around for "XFSB" in the early few blocks
>> of your raid and see if the raid might possibly have been rebuilt
>> out of order.
>>
>> # dd if=/dev/md0 bs=4k count=32 | hexdump -C | grep XFSB
>>
>> or so...
>>
>> -Eric
>
> No, I didn't find this - I did find some disk ID header stuff which
> confirms that the filesystem is XFS and some other info that might be
> useful, but no XFSB strings, even grepping 8MB into the device.
>
> |<IPStorPartition|
> | version="3.0" s|
> |ize="595" owner=|
> |"NACS-SW-DIST" c|
> |hecksum="" signa|
> |ture="IpStOrDyNa|
> |MiCdIsK" dataSta|
> |rtAtSectorNo="16|
.... knowing the offsets of these might be helpful. But perhaps you are
simply not trying to mount the thing which actually has xfs on it.
I don't know what IPStore is. Perhaps your volume is encrypted?
Dunno... at any rate, doesn't seem at first glance like it's an xfs
problem, I'm afraid.
> |firstSector="222|
> |72" lastSector="|
> |2928740095" owne|
I might look at sector 22272 (about 10MB in) and see if that looks like
xfs :)
Or maybe just put it back in the NAS box, now, assembled the same way.
-Eric
> |128" logvol="0" |
> |category="Virtua|
> |l Device"/>.<Phy|
> |sicalDev guid="5|
> |95e9fbb-1951-09c|
> |3-a30c-000045d3a|
> |a3b" Comment="" |
> |WorldWideID="FAL|
> |CON LVMDISK-M09|
> |N01 v1.0-0-0-00|
> |"/>.............|
> |................|
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-02-23 21:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 20:43 XFS on ARM-based Linux on USR8700 NAS appliance w/ mdadm/RAID5 Harry Mangalam
2009-02-23 20:53 ` Eric Sandeen
2009-02-23 21:20 ` Harry Mangalam
2009-02-23 21:31 ` Eric Sandeen [this message]
2009-02-23 21:45 ` Harry Mangalam
2009-02-23 21:54 ` Eric Sandeen
2009-02-23 22:24 ` Harry Mangalam
2009-02-23 22:31 ` 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=49A315BE.7090607@sandeen.net \
--to=sandeen@sandeen.net \
--cc=harry.mangalam@uci.edu \
--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