> Hi Nicolas, > > > Using FAI 3.4~beta6+experimental2 (also checked with experimental4 > > this morning) for squeeze and LVM, I have a funny fstab problem. > > > > setup-storage looks in /dev/<LVM volume> during installation to > > build /etc/fstab: > > > > (CMD) readlink -f /dev/vg0/var 1> /tmp/mPvYMCBCMk 2> /tmp/TcD7OA66rq > > Executing: readlink -f /dev/vg0/var > > (STDOUT) /dev/dm-0 > > [...] > > (CMD) readlink -f /dev/vg0/swap 1> /tmp/ls625DMAbK 2> /tmp/cAQYclvajY > > Executing: readlink -f /dev/vg0/swap > > (STDOUT) /dev/dm-1 > > [...] > > > > But when the host boots, the links are all mixed up, so it doesn't > > work so well: > > > > # readlink /dev/vg0/var > > ../dm-1 > > # readlink /dev/vg0/swap > > ../dm-2 > > ... > > > > Shouldn't setup-storage use links in /dev/<volume> or /dev/mapper, > > or even UUIDs, rather than /dev/dm-* , for /etc/fstab? > > > > Thanks for the report and debugging effort. Hmm, so doing the readlink thing > is > not a good idea it seems, maybe we should change this, yes. But for the moment > I'd suggest you just go for UUIDs, which we might want to make the default. > You > can achieve this by adding > > fstabkey:uuid > > to your disk/LVM config line, like > > disk_config lvm fstabkey:uuid >
This should now be fixed as of 4.0~beta2+experimental5; more info to follow in thread titled "setup-storage problem with lvm and fstabkey:uuid vs fstabkey:device". Best, Michael
pgp6sG8pJOJ8C.pgp
Description: PGP signature
