David Christensen <dpchrist@holgerdanske.com> writes:
AIUI the OP was mounting an (external?) drive partition for use as a
destination for backups. Prior to upgrading to Testing, the root
partition was /dev/sda1 (no LVM?) and the backup partition was
/dev/sdb1 (no LVM?). After upgrading to Testing, the root partition
is /dev/sdb1 and the backup partition device node is unknown. The OP
was confused by the changed root partition device node.
Please describe how LVM would help in this situation.
Instead of using /dev/sdb1 directly for the backup file system, the OP
could put LVM to /dev/sdb1 (or now /dev/sda1). I.e. he would create a
physical volume on /deb/sdb1, create a volume group e.g. named vgbkup,
and would then create a logical volume, e.g. named lv1. The device
name for the backup file system would then always be /dev/vgbkup/lv1
regardless of how the kernel will name underlying device (/dev/sda1 or
/dev/sdb1 or whatever).
In addition, you get the flexibility of LVM of adding, deleting, and
resizing volumes without re-partitioning.