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 16:31:07 -0600 [thread overview]
Message-ID: <49A323AB.4050104@sandeen.net> (raw)
In-Reply-To: <200902231424.25130.harry.mangalam@uci.edu>
Harry Mangalam wrote:
> mount -t xfs -o loop,offset=11403264,ro,norecovery /dev/md0 /lost
>
> gives me a mount(!!):
>
> df -> /lost/public, but it's not a standard entry:
> ?--------- ? ? ? ? ? /lost/public
>
> and dmesg coughs up many lines of XFS errors:
not sure at this point. i'd put it back in the nas box w/ the recreated
raid mount -o ro,norecovery again for safety if you like, and hope for
the best.
Otherwise maybe run repair; on a dd image if you prefer, again for
safety....
-Eric
> loop: AES key scrubbing enabled
> loop: loaded (max 8 devices)
> Filesystem "loop0": Disabling barriers, not supported by the
> underlying device
> Mounting filesystem "loop0" in no-recovery mode. Filesystem will be
> inconsistent.
> XFS resetting qflags for filesystem loop0
> xfs_force_shutdown(loop0,0x1) called from line 424 of file
> fs/xfs/xfs_rw.c. Return address = 0xfb2fc728
> Filesystem "loop0": I/O Error Detected. Shutting down filesystem:
> loop0
> Please umount the filesystem, and rectify the problem(s)
> xfs_force_shutdown(loop0,0x1) called from line 424 of file
> fs/xfs/xfs_rw.c. Return address = 0xfb2fc728
> Filesystem "loop0": Disabling barriers, not supported by the
> underlying device
> Mounting filesystem "loop0" in no-recovery mode. Filesystem will be
> inconsistent.
> XFS resetting qflags for filesystem loop0
>
>
>
>
> On Monday 23 February 2009, Eric Sandeen wrote:
>> 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
>
>
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-02-23 22:31 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
2009-02-23 22:24 ` Harry Mangalam
2009-02-23 22:31 ` Eric Sandeen [this message]
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=49A323AB.4050104@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.