From: NeilBrown <neilb@suse.de>
To: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: md device is read only mode
Date: Tue, 10 Jul 2012 07:42:01 +1000 [thread overview]
Message-ID: <20120710074201.76846af5@notabene.brown> (raw)
In-Reply-To: <20120709173406.GA4206@lazy.lzy>
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
On Mon, 9 Jul 2012 19:34:07 +0200 Piergiorgio Sartor
<piergiorgio.sartor@nexgo.de> wrote:
> Hi Neil,
>
> please see one comment below.
>
> On Mon, Jul 09, 2012 at 11:40:22AM +1000, NeilBrown wrote:
> [...]
> > The mount system call will notice that the device is read-only, and will make
> > assume the read-only mount option.
>
> OK, so it should work as expected.
>
> The story was this.
> After fixing the RAID-5 superblock problem, we
> wanted to see if the filesystem was still OK.
> So we started the RAID in r/o mode (so to avoid
> any possible further damage from mount) and then
> mounted the filesystem (actually, now that I
> think of it, there was an LVM layer in the middle).
> This mount caused a kernel error report (I do
> not know if BUG() or else).
>
> Is there any explanation for that?
Probably LVM isn't detecting that the underlying device is readonly and so
forcing the upper device to be readonly.
md doesn't do this either - it should.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-07-09 21:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 17:27 md device is read only mode Piergiorgio Sartor
2012-07-09 1:40 ` NeilBrown
2012-07-09 17:34 ` Piergiorgio Sartor
2012-07-09 21:42 ` NeilBrown [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=20120710074201.76846af5@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=piergiorgio.sartor@nexgo.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).