All of lore.kernel.org
 help / color / mirror / Atom feed
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:54:05 -0600	[thread overview]
Message-ID: <49A31AFD.8070804@sandeen.net> (raw)
In-Reply-To: <200902231345.25062.harry.mangalam@uci.edu>

Harry Mangalam wrote:
> On Monday 23 February 2009, Eric Sandeen wrote:
>>> |<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 :)
> 
> Good guess! :
> At 00AE0000 (11.4MB in) there's "XFSB" altho I can't make out much of 
> the surrounding bytes...
> 
> Is there a way to do anything with this info?  Can it be dd'ed out to 
> use to get the thing mounted?

try mount -o loop,offset=11403264 /dev/whatever /mnt/whatever

I'd probably also add ro,norecovery to the options as well so you don't
actually write anything to it at this point.

-Eric

>> Or maybe just put it back in the NAS box, now, assembled the same
>> way.
> 
> This is just about my last gasp - I'll rec that they try this if 
> nothing else comes to mind..
>> -Eric
> 
> 
> 

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-02-23 22:04 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
2009-02-23 21:45       ` Harry Mangalam
2009-02-23 21:54         ` Eric Sandeen [this message]
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=49A31AFD.8070804@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 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.