public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Harry Mangalam <harry.mangalam@uci.edu>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: XFS on ARM-based Linux on USR8700 NAS appliance w/ mdadm/RAID5
Date: Mon, 23 Feb 2009 14:24:24 -0800	[thread overview]
Message-ID: <200902231424.25130.harry.mangalam@uci.edu> (raw)
In-Reply-To: <49A31AFD.8070804@sandeen.net>

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:

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



-- 
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.]

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

  reply	other threads:[~2009-02-23 22:22 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 [this message]
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=200902231424.25130.harry.mangalam@uci.edu \
    --to=harry.mangalam@uci.edu \
    --cc=sandeen@sandeen.net \
    --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