From: Emmanuel Florac <eflorac@intellique.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: can't mount XFS from a read-only device
Date: Fri, 9 Oct 2009 21:21:50 +0200 [thread overview]
Message-ID: <20091009212150.2b54cb77@galadriel.home> (raw)
In-Reply-To: <4ACF8801.7070009@sandeen.net>
Le Fri, 09 Oct 2009 13:59:13 -0500 vous écriviez:
> try mount -o norecovery (and maybe -o nobarrier)
Thank you, that worked.
I can't help but think that when given the "ro" option, XFS shouldn't
try to write a single bit to the underlying device, or else what's the
point?
--
--------------------------------------------------
Emmanuel Florac www.intellique.com
--------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-10-09 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 15:09 can't mount XFS from a read-only device Emmanuel Florac
2009-10-09 18:59 ` Eric Sandeen
2009-10-09 19:21 ` Emmanuel Florac [this message]
2009-10-09 19:28 ` Eric Sandeen
2009-10-09 19:50 ` Emmanuel Florac
[not found] ` <20091009174351.GB13572@dora.cern.ch>
2009-10-09 19:19 ` Emmanuel Florac
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=20091009212150.2b54cb77@galadriel.home \
--to=eflorac@intellique.com \
--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 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.