I recently upgraded a stock Fedore Core 4 kernel on a Sun V20z dual Opteron box to a 2.6.14-1.1656_FC4smp kernel and was suprised to find what had been /dev/sda is now identified as /dev/sdb, and vice-versa. Interestingly, everthing seems to work OK, I guess because GRUB is working off of disk labels rather than device names (?), but my question is what gotchas might be waiting for me down the road? I don't expect to be modifying this setup at all, if that matters. I included some filesystem-specific stuff below in case it has any relevance to my question. Hardware is a hardware RAID1 (2 local SCSI disks using motherboard-supported SCSI) and an LSI FibreChannel card. jc@rs2-dev2:~$ cat /etc/fstab # This file is edited by fstab-sync - see 'man fstab-sync' for details LABEL=/ / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 LABEL=/data01 /data01 ext3 defaults 1 2 LABEL=/data02 /data02 ext3 defaults 1 2 /dev/devpts /dev/pts devpts gid=5,mode=620 0 0 /dev/shm /dev/shm tmpfs defaults 0 0 LABEL=/home /home ext3 defaults 1 2 /dev/proc /proc proc defaults 0 0 /dev/sys /sys sysfs defaults 0 0 LABEL=/tmp /tmp ext3 defaults 1 2 LABEL=/usr /usr ext3 defaults 1 2 LABEL=/var /var ext3 defaults 1 2 LABEL=SWAP-sda7 swap swap defaults 0 0 jc@rs2-dev2:~$ df -k Filesystem 1K-blocks Used Available Use% Mounted on /dev/sdb3 1019240 247936 718692 26% / /dev/sdb1 77749 18088 55647 25% /boot /dev/sdb9 103237296 110272 97798268 1% /data01 /dev/sda1 948728940 121740 899637068 1% /data02 /dev/shm 2029612 0 2029612 0% /dev/shm /dev/sdb6 10153988 55940 9573932 1% /home /dev/sdb5 10153988 217688 9412184 3% /tmp /dev/sdb2 8029884 1276008 6339400 17% /usr /dev/sdb8 2030736 127940 1797976 7% /var jc@rs2-dev2:~$ cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: Xyratex Model: 4200 Rev: 342D Type: Direct-Access ANSI SCSI revision: 03 Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: LSILOGIC Model: 1030 IM IM Rev: 1000 Type: Direct-Access ANSI SCSI revision: 02
