On Tue, Oct 28, 2014 at 9:06 PM, Phillip Susi <[email protected]> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On 10/28/2014 09:55 PM, Jason Gunthorpe wrote:
> > Fundamentally, if /dev/sda has a valid RAID label then it *MUST* be setup
> > and accessed through the dmraid device and *NEVER* via /dev/sda.
> >
> > Otherwise the installer will see a disc that is too big and it will
> destroy
> > the RAID label at the end of the disc, then the system will not boot.
>
> For MBR partitioned disks this isn't really a problem because they never
> really use the last bit of the disk anyhow, but for GPT, yes... that
> would be a problem.
>
Except "never really use" means "don't fill up the filesystem". If the FS
uses the last portion of the partition it will corrupt the RAID label and
restoring the RAID label will corrupt the FS. Which is pretty bad, but not
immediate.
> FWIW, RHEL gets this right and sets up dmraid on this disc.
>
> Interesting.. they must have a patch that hasn't been upstreamed.
>
Looks like they have a dracut specific version, it seems much saner, no
crazy parsing of dmraid output.
info "Scanning for dmraid devices $DM_RAIDS"
SETS=$(dmraid -c -s)
if [ "$SETS" = "no raid disks" -o "$SETS" = "no raid sets" ]; then
return
fi
[..]
# scan and activate all DM RAIDS
for s in $SETS; do
info "Activating $s"
dmraid -ay -i -p --rm_partitions "$s" 2>&1 | vinfo
[ -e "/dev/mapper/$s" ] && kpartx -a -p p "/dev/mapper/$s" 2>&1 |
vinfo
done
Jason
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361842
Title:
dmraid does not start on boot for single disk RAID0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/1361842/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
