On 9 Feb 2010, at 15:27, J. Roeleveld wrote:
On Tuesday 09 February 2010 16:11:14 Stroller wrote:
On 9 Feb 2010, at 13:57, J. Roeleveld wrote:
...
With Raid (NOT striping) you can remove one disk, leaving the Raid-
array in a
reduced state. Then repartition the disk you removed, repartition
and then re-
add the disk to the array.
Exactly. Except the partitions extend, in the same positions, across
all the disks.
You cannot remove one disk from the array and repartition it, because
the partition is across the array, not the disk. The single disk,
removed from a RAID 5 (specified by Paul Hartman) array does not
contain any partitions, just one stripe of them.
I apologise if I'm misunderstanding something here, or if your RAID
works differently to mine.
Stroller, it is my understanding that you use hardware raid adapters?
Yes.
If that is the case, then the mentioned method won't work for you ...
I believe Paul Hartman is, like me, using Linux Sofware raid (mdadm
+kernel
drivers).
In that case, you can do either of the following:
Put the whole disk into the RAID, eg:
mdadm --create --level=5 --devices=6 /dev/sd[abcdef]
Or, you create 1 or more partitions on the disk and use these, eg:
mdadm --create --level=5 --devices=6 /dev/sd[abcdef]1
Thank you for identifying the source of this misunderstanding.
and if your raid-adapters already align everything properly, then
you shouldn't notice any problems with these drives.
It would, however, be interesting to know how hardware raid adapters
handle these 4KB sector-sizes.
I think my adaptor at least, being older, may very well be prone to
this problem. I discussed this in my post of 8 February 2010 19:57:46
GMT - certainly I have a RAID array aligned beginning at sector 63,
and it is at least a little slow. I will test just as soon as I can
afford 3 x 1TB drives.
I think the RAID adaptor would have to be quite "clever" to avoid this
problem. It may be a feature added in newer controllers, but that
would be a special attempt to compensate. I think in the general case
the RAID controller should just consolidate 3 x physical block devices
(or more) into 1 x virtual block device, and should not do anything
more complicated that this. I am sure that a misalignment will
propagate downwards through the levels of obscusification.
IMO this is a fdisk "bug". A feature should be added so that it tries
to align optimally in most circumstances. RAID controllers should not
be trying to do anything clever to accommodate potential misalignment
unless it is really cheap to do so.
Stroller.
