From: CoolCold <coolthecold@gmail.com>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Fwd: mounting component device of RAID1 with internal bitmap
Date: Fri, 2 Apr 2010 18:39:18 +0400 [thread overview]
Message-ID: <n2mf19d625d1004020739oade0211ap1def8afa5c2d8e89@mail.gmail.com> (raw)
In-Reply-To: <4BB4F548.2090709@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2102 bytes --]
Just to share this with list.
---------- Forwarded message ----------
From: Doug Ledford <dledford@redhat.com>
Date: Thu, Apr 1, 2010 at 11:34 PM
Subject: Re: mounting component device of RAID1 with internal bitmap
To: CoolCold <coolthecold@gmail.com>
On 04/01/2010 03:25 PM, CoolCold wrote:
> On Thu, Apr 1, 2010 at 10:39 PM, Doug Ledford <dledford@redhat.com> wrote:
>> On 04/01/2010 02:26 PM, CoolCold wrote:
>>> On Thu, Apr 1, 2010 at 10:14 PM, Doug Ledford <dledford@redhat.com> wrote:
>>>> On 04/01/2010 01:47 PM, CoolCold wrote:
>>>>> Hello!
>>>>> For raid1 array with metadata 0.90 it is possible to mount component
>>>>> (let's say /dev/sda1) as usual FS, fix smth, /etc/fstab for example,
>>>>> unmount and then assamble arary.
>>>>
>>>> At which point you have just corrupted your array.
>>> I've did such operation several times and it worked fine..I'll do some
>>> checks and report later.
>>
>> Because you got lucky. When you do this, you make the different members
>> of the raid array disagree on the contents of whatever file you
>> modified. Depending on which disk the kernel reads from, you will get
>> either the new or the old contents of the file. Any time you mount a
>> component device and modify it, you *must* force a resync from that
>> component to all other components or you *will* have a corrupt array.
>> When that corruption will crop up to bite you in the ass is up to random
>> chance.
> Ah, ofcourse recync is ok , i wanted to know will this break _raid_
> (eg erase some metadata) itself, not actual data on top of it. For 0.9
> it is said in man that it stored at the end of device, but what about
> bitmaps? are they at the end too ?
The bitmaps are outside of the regular filesystem area, so they can't be
harmed by mounting the filesystem.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: CFBFF194
http://people.redhat.com/dledford
Infiniband specific RPMs available at
http://people.redhat.com/dledford/Infiniband
--
Best regards,
[COOLCOLD-RIPN]
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-04-02 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 17:47 mounting component device of RAID1 with internal bitmap CoolCold
2010-04-01 18:14 ` Doug Ledford
2010-04-01 18:26 ` CoolCold
2010-04-01 18:39 ` Doug Ledford
[not found] ` <l2hf19d625d1004011225q850be4an64d7bcb6d5604dc7@mail.gmail.com>
[not found] ` <4BB4F548.2090709@redhat.com>
2010-04-02 14:39 ` CoolCold [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=n2mf19d625d1004020739oade0211ap1def8afa5c2d8e89@mail.gmail.com \
--to=coolthecold@gmail.com \
--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 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).