From: Neil Brown <neilb@suse.de>
To: Martin Cracauer <cracauer@cons.org>
Cc: John Robinson <john.robinson@anonymous.org.uk>,
linux-raid@vger.kernel.org
Subject: Re: Superblock V 1.2
Date: Tue, 16 Nov 2010 07:11:30 +1100 [thread overview]
Message-ID: <20101116071130.3ed4871e@notabene.brown> (raw)
In-Reply-To: <20101115195220.GA27668@cons.org>
On Mon, 15 Nov 2010 14:52:20 -0500
Martin Cracauer <cracauer@cons.org> wrote:
> Neil Brown wrote on Tue, Nov 16, 2010 at 06:47:46AM +1100:
> > On Mon, 15 Nov 2010 11:16:46 -0500
> > Martin Cracauer <cracauer@cons.org> wrote:
> >
> > > Neil Brown wrote on Mon, Nov 15, 2010 at 12:11:58PM +1100:
> > > >
> > > > When mdadm does auto-assemble an array that doesn't obviously belong to this
> > > > host, it tries to be careful and assembles it 'read-auto', which means that
> > > > it is completely read-only until you try to write to the array. So no
> > > > recovery or resync happens.
> > > > Once you write to the array, md assumes that you are happy to have the array
> > > > assembled on this device, and allows any resync etc to start.
> > >
> > > Speaking of which, are there any plans to do a true readonly mode?
> > >
> > > I missed that quite a few times.
> > >
> > > Martin
> >
> > In what does
> > mdadm --readonly /dev/mdXX
> >
> > not meet your needs?
> > (which is to say: I think there is a true readonly mode, but I've never
> > seriously used it so don't know for certain that it is actually useful).
>
> Isn't that the mode that upgrades to read-write when you write?
>
No.
NeilBrown
prev parent reply other threads:[~2010-11-15 20:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-07 19:15 Superblock V 1.2 Martin Cracauer
2010-11-07 21:03 ` Leslie Rhorer
2010-11-07 21:08 ` Martin Cracauer
2010-11-07 21:39 ` John Robinson
2010-11-09 16:35 ` Martin Cracauer
2010-11-09 17:08 ` John Robinson
2010-11-15 1:11 ` Neil Brown
2010-11-15 16:16 ` Martin Cracauer
2010-11-15 19:47 ` Neil Brown
2010-11-15 19:52 ` Martin Cracauer
2010-11-15 20:11 ` Neil Brown [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=20101116071130.3ed4871e@notabene.brown \
--to=neilb@suse.de \
--cc=cracauer@cons.org \
--cc=john.robinson@anonymous.org.uk \
--cc=linux-raid@vger.kernel.org \
/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.