----- Original Message -----
From: "Peter Jones" <pjones@xxxxxxxxxx>
OK, that should be in rawhide in the next couple of days. Hopefully
tomorrow, but the build boxes are a little crowded recently.
Peter,
Several of us have a Fake RAID boxes (mine shuttle's are via chipsets) and
are chomping at the bits to try the latest dmraid. In order to give you
maximum feedback in chronological order, could you put a complete set of
instructions and diagnostic commands to use over at
http://fedoraproject.org/wiki/DmraidStatus?
For example:
1. Non-upgrade Install rawhide on two pre-mirrored drives.
1a. After firstboot, save all metadata for reference. (fstab, blkid.tab,
grub.conf, lvm.conf, pvdisplay, dmraid -rvv, dmsetup table)
1b. Disconnect secondary drive and boot on primary drive only, save all
metadata for reference.
1c. Disconnect primary drive and boot on secondary drive only, save all
metadata for reference.
1d. Reconnect both drives, resync drives in BIOS and boot, save all
metadata for reference. (1a and 1d metadata should match?)
1e. Upgrade kernel, save all metadata for reference.
2. Non-upgrade Install rawhide on one drives (even with BIOS set the RAID
enabled).
2a. After firstboot, save all metadata for reference.
2b. Connect secondary drive and establish mirror in BIOS. Boot and save
all metadata for reference. (should match 1a metadata?)
3c. Upgrade kernel, save all metadata for reference.
This all won't be at all tedious if you just put together a script for us to
snapshot a version of the metadata.
As an aside, I just find it extremely frightening that inserting and
ejecting removable media has the system rewrites a file as important as
fstab on every little whim. I feel that a transient media should have their
own fstab file to mess up.
thanks!
-eric wood
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
