From: Harry Mangalam <harry.mangalam@uci.edu>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: rescue an alien md raid5
Date: Mon, 23 Feb 2009 12:04:39 -0800 [thread overview]
Message-ID: <200902231204.39660.harry.mangalam@uci.edu> (raw)
In-Reply-To: <ae41ed6f5db4a30599973b9466f89e19.squirrel@neil.brown.name>
On Monday 23 February 2009, NeilBrown wrote:
> On Tue, February 24, 2009 5:13 am, Harry Mangalam wrote:
> > Here's an unusual (long) tale of woe.
> >
> > We had a USRobotics 8700 NAS appliance with 4 SATA disks in
> > RAID5:
> > <http://www.usr.com/support/product-template.asp?prod=8700> which
> > was a fine (if crude) ARM-based Linux NAS until it stroked out at
> > some point, leaving us with a degraded RAID5 and comatose NAS
> > device.
> >
> > We'd like to get the files back of course and I've moved the
> > disks to a Linux PC, hooked them up to a cheap Silicon Image 4x
> > SATA controller and brought up the whole frankenmess with mdadm.
> > It reported a clean but degraded array:
>
> Isn't it nice that it was Linux inside that box, rather than some
> proprietary OS with some undocumented raid metadata....
And that it used mdadm.. - /IT/ worked perfectly.
> > The docs and files on the USR web site imply that the native
> > filesystem was originally XFS, but when i try to mount it as
> > such, I can't:
>
> I heard Dave Chinner talking about this during LCA-2009.
> If I remember correctly, there is something a bit funny about
> structure layout and padding on the ARM and it affects XFS is some
> strange way, and some NAS vendors 'fixed' it the wrong way, so they
> are incompatible with mainline..... or something like that. What I
> really remember is ARM + XFS + NAS == BAD Vendor
>
> I suggest asking at xfs@oss.sgi.com
Thanks - I'll go over and bug them a bit before I give up.
>
> No, those other partitions are relevant. One was clearly for
> swap. The other was probably /boot.
Yes, I now remember that it did provide a small /boot (+ a bit of OS
space). I added some utils there while I was testing it before I
decided it was too much effort for the return.
Thanks very much for the note.
--
Harry Mangalam - Research Computing, NACS, E2148, Engineering Gateway,
UC Irvine 92697 949 824-0084(o), 949 285-4487(c)
---
Good judgment comes from experience;
Experience comes from bad judgment. [F. Brooks.]
next prev parent reply other threads:[~2009-02-23 20:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 18:13 rescue an alien md raid5 Harry Mangalam
2009-02-23 18:58 ` Joe Landman
2009-02-23 19:59 ` Harry Mangalam
2009-02-23 19:14 ` NeilBrown
2009-02-23 20:04 ` Harry Mangalam [this message]
2009-03-02 11:22 ` Nagilum
2009-03-02 16:57 ` Harry Mangalam
2009-02-24 0:56 ` hgichon
2009-02-24 21:11 ` Harry Mangalam
2009-03-14 14:12 ` Ryan Wagoner
2009-03-14 18:15 ` Harry Mangalam
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=200902231204.39660.harry.mangalam@uci.edu \
--to=harry.mangalam@uci.edu \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).