On Fri, May 23, 2008 at 01:41:32PM -0400, Gerry Reno wrote:
> We have a new machine which has SATA. This is the first machine we have
> had with SATA. SATA and these changing device locations are giving me a
> headache. None of our disk device tools work with SATA. For instance
> we have a tool that will save all the MBR's and partition tables off to
> files such as 'hda.mbr' and 'hda.part'. With SATA this does not work
> because what was 'sda' during this boot may be 'sdc' on the next boot.
> So I need to find out if there is some best practice guide for how to
> rewrite our tools so that they can support SATA. We use LVM over RAID
> on all our drives and all our RAID and LVM tools appear to still work.
> It is only when dealing with the low-level disk devices themselves that
> we have problems. Can someone give me some suggestions as to how to
> manage things when using SATA?
If you want stable device names, don't use /dev/sd* at all.
This is what /dev/disk/by-{id,label,path,uuid}/* are for
Dan.
--
|: Red Hat, Engineering, Boston -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
