From: David Chow <davidchow@shaolinmicro.com>
To: neilb@cse.unsw.edu.au
Cc: linux-raid@vger.kernel.org
Subject: readonly start of Linux RAID
Date: Wed, 29 Jan 2003 01:49:55 +0800 [thread overview]
Message-ID: <3E36C2C3.3070101@shaolinmicro.com> (raw)
Hi Neil,
I've been reading some archives in the Linux RAID mailing list. Someone ask for implementing a readonly mode instead of degraded mode in RAID-1/5 setups. I'm falling into a similar problem . I think it is important to have a readonly mode on starting a RAID device or operating on a RAID device. Think of systems that didn't want to rebuild their RAID immediately after an unclean shutdown... Calling autorun() ioctls will make all devices starting rebuild themselves in case of any available disk exists. In case we are on a shared storage system, the active cluster might have using the RAID disks which seems to be unclean on the other standby cluster. The standby cluster might want to have a read-only inspection of the shared storage. In case of a high availability cluster system failover, the standby cluster might want to determine to start full read/write access by some tools instead of forced automatic at system boot (initrd calling raidautorun). In such circumstances, the cur
rent md driver cannot be used. This also prohibits many implementation of a high availability system from implement linux RAID on a shared storage on an HA system which is extremely important. I guess, this problem also comes with LVM and other similar volume management system. I'm currently studying the md.c code in a 2.4.19 kernel which I see implementing a read-only mode for md is possible. Please give advice or anything happening, so that I don't spend duplicated efforts. Thanks.
regards,
David Chow
next reply other threads:[~2003-01-28 17:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 17:49 David Chow [this message]
2003-01-28 18:28 ` readonly start of Linux RAID Steven Dake
2003-01-29 3:02 ` David Chow
2003-01-29 16:53 ` Steven Dake
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=3E36C2C3.3070101@shaolinmicro.com \
--to=davidchow@shaolinmicro.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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).