From: "Williams, Dan J" <dan.j.williams@intel.com>
To: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@intel.com>
Cc: neilb@suse.de, linux-raid@vger.kernel.org, ed.ciechanowski@intel.com
Subject: Re: [PATCH 4/4] imsm: monitor: do not finish recovery, when raid goes to read-only
Date: Thu, 5 Apr 2012 10:37:15 -0700 [thread overview]
Message-ID: <CABE8wwsGehaT1xpYWSwX8yogqNEYw3GtSjROwohnH_ev17iBtg@mail.gmail.com> (raw)
In-Reply-To: <20120405153126.19851.45474.stgit@linux.site>
On Thu, Apr 5, 2012 at 8:31 AM, Przemyslaw Czarnowski
<przemyslaw.hawrylewicz.czarnowski@intel.com> wrote:
> If kernel forces raid to be read-only (eg. during reboot, and root
> partition lies on array) monitor should not finish recovery and leave
> metadata untouched.
I'm not sure I understand the point of this one, can you clarify?
Even though the rootfs is readonly at initial boot it may still
require the root block device to be readwrite. For example xfs needs
to do journal playback even when mounting ro. So if the monitor is
running at all it means that the array was started read-write (or at
least read-auto) and should be fine to complete recovery.
--
Dan
next prev parent reply other threads:[~2012-04-05 17:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 15:28 [PATCH 0/4] Imsm OROM compatibility/boot support fixes Przemyslaw Czarnowski
2012-04-05 15:29 ` [PATCH 1/4] imsm: monitor: do not finish migration if there are no failed disks Przemyslaw Czarnowski
2012-04-05 17:56 ` Williams, Dan J
2012-04-05 15:30 ` [PATCH 2/4] imsm: clean up missing disks if there are any left after migration Przemyslaw Czarnowski
2012-04-05 17:06 ` Williams, Dan J
2012-04-05 15:30 ` [PATCH 3/4] imsm: avoid double change of serial number of missing device Przemyslaw Czarnowski
2012-04-05 17:41 ` Williams, Dan J
2012-04-05 15:31 ` [PATCH 4/4] imsm: monitor: do not finish recovery, when raid goes to read-only Przemyslaw Czarnowski
2012-04-05 17:37 ` Williams, Dan J [this message]
2012-04-09 23:22 ` [PATCH 0/4] Imsm OROM compatibility/boot support fixes NeilBrown
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=CABE8wwsGehaT1xpYWSwX8yogqNEYw3GtSjROwohnH_ev17iBtg@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=ed.ciechanowski@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=przemyslaw.hawrylewicz.czarnowski@intel.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;
as well as URLs for NNTP newsgroup(s).