Bookmarks

Yahoo Gmail Google Facebook Delicious Twitter Reddit Stumpleupon Myspace Digg

Search queries

WWWXXXAPC, docmd.close 2585, WWWXXXDOCO, nu vot, dhcpd lease file "binding state", WWWXXXDOCO, how to setup procmail to process html2text, how to setup procmail html2text, WWWXXXAPC., XXXCNZZZ

Links

XODOX
Impressum

#1: repartitioning disks

Posted on 2011-05-17 10:20:50 by CoolCold

Wiki says: "Never NEVER never re-partition disks that are part of a
running RAID. If you must alter the partition table on a disk which is
a part of a RAID, stop the array first, then repartition. " -
https://raid.wiki.kernel.org/index.php/Tweaking,_tuning_and_ troubleshooting#Pitfalls

Is it really true for situations like - I have 2x1Tb drives, which are
already partitioned like /dev/sd{a,b}1 - 500mb, /boot & /dev/sd{a,b}2
- 20gb, / and are assembled in RAID1 arrays md0 & md1 accordingly. So,
if I want to create one more RAID1 array , say md3 from the rest of
the drives.
So i take my cfdisk ,add new partition with some space 100-150mb from
the end, do write changes & partprobe the drives, then creating new
array.

Is it bad? To be honest i'm doing this all the time and can't
understand how this gonna hurt md. Neil and/or others, please clarify
this.


--
Best regards,
[COOLCOLD-RIPN]
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Report this message

#2: Re: repartitioning disks

Posted on 2011-05-17 12:39:44 by NeilBrown

On Tue, 17 May 2011 12:20:50 +0400 CoolCold <coolthecold@gmail.com> wrote:

> Wiki says: "Never NEVER never re-partition disks that are part of a
> running RAID. If you must alter the partition table on a disk which is
> a part of a RAID, stop the array first, then repartition. " -
> https://raid.wiki.kernel.org/index.php/Tweaking,_tuning_and_ troubleshooting#Pitfalls
>
> Is it really true for situations like - I have 2x1Tb drives, which are
> already partitioned like /dev/sd{a,b}1 - 500mb, /boot & /dev/sd{a,b}2
> - 20gb, / and are assembled in RAID1 arrays md0 & md1 accordingly. So,
> if I want to create one more RAID1 array , say md3 from the rest of
> the drives.
> So i take my cfdisk ,add new partition with some space 100-150mb from
> the end, do write changes & partprobe the drives, then creating new
> array.
>
> Is it bad? To be honest i'm doing this all the time and can't
> understand how this gonna hurt md. Neil and/or others, please clarify
> this.
>
>

There shouldn't be any problem with that as long as you are careful (and if
you aren't careful, there are plenty of other ways to destroy your data).

I wasn't aware of partprobe. Just telling the kernel to reread the
partition table won't work when a partition is in use.
But partprobe seems to just tell the kernel about the partitions that have
changed, using a different ioctl, and that seem to work.

NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Report this message

#3: Re: repartitioning disks

Posted on 2011-05-17 14:31:04 by CoolCold

On Tue, May 17, 2011 at 2:39 PM, NeilBrown <neilb@suse.de> wrote:
> On Tue, 17 May 2011 12:20:50 +0400 CoolCold <coolthecold@gmail.com> w=
rote:
>
>> Wiki says: "Never NEVER never re-partition disks that are part of a
>> running RAID. If you must alter the partition table on a disk which =
is
>> a part of a RAID, stop the array first, then repartition. " -
>> https://raid.wiki.kernel.org/index.php/Tweaking,_tuning_and_ troubles=
hooting#Pitfalls
>>
>> Is it really true for situations like - I have 2x1Tb drives, which a=
re
>> already partitioned like /dev/sd{a,b}1 - 500mb, /boot & /dev/sd{a,b}=
2
>> - 20gb, / and are assembled in RAID1 arrays md0 & md1 accordingly. S=
o,
>> if I want to create one more RAID1 array , say md3 from the rest of
>> the drives.
>> So i take my cfdisk ,add new partition with some space 100-150mb fro=
m
>> the end, do write changes & partprobe the drives, then creating new
>> array.
>>
>> Is it bad? To be honest i'm doing this all the time and can't
>> understand how this gonna hurt md. Neil and/or others, please clarif=
y
>> this.
>>
>>
>
> There shouldn't be any problem with that as long as you are careful (=
and if
> you aren't careful, there are plenty of other ways to destroy your da=
ta).
>
> I wasn't aware of partprobe. =A0 =A0Just telling the kernel to reread=
the
> partition table won't work when a partition is in use.
> But partprobe seems to just tell the kernel about the partitions that=
have
> changed, using a different ioctl, and that seem to work.
Hmm..when I'm adding new partitions (or even deleting partitions which
are not part of any array), i'm not changing the existing ones, which
are part of arrays, and even without partprobe this action should be
ok, as it doesn't do anything to md's metadata ?
Updating partition which is part of running array going to be bad
thing, this is clear for me.

>
> NeilBrown
>



--=20
Best regards,
[COOLCOLD-RIPN]
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Report this message