Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1204936

Bug#1072996: /dev/mapper/ nodes being renamed

Show all headers | View raw

Thanks Agustin & Leandro for highlighting this issue, and for finding a
workaround.

After some investigation, I think I have narrowed the problem down to
changes in behaviour of the automatic setup of entries in the /dev/
filesystem with the newer trixie tooling. It appears that although it
was safe to assume that cryptmount devices would always be named
"/dev/mapper/<target_name>", there is a tendency for these to be
automatically renamed into symlinks of the form
"/dev/disk/by-id/dm-name-<target_name>". This even appears to occur when
mke2fs is run on a a device in /dev/mapper/, which subsequently disappears.

I'm currently exploring how best to handle this portably within
cryptmount, perhaps via dm_device_get_name(), but it's obviously awkward
that we can no longer just use dm_dir() as the path prefix for devices
created by cryptmount.

RW Penney

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Bug#1072996: cryptmount: No longer working with current sid (e2fsck error) Agustin Martin <agmartin@debian.org> - 2024-06-11 15:50 +0200
  Bug#1072996: cryptmount: No longer working with current sid (e2fsck error) Leandro Lisboa Penz <lpenz@lpenz.org> - 2024-06-27 13:10 +0200
    Bug#1072996: cryptmount: No longer working with current sid (e2fsck error) Agustin Martin <agmartin@debian.org> - 2024-07-18 00:10 +0200
  Bug#1072996: /dev/mapper/ nodes being renamed deb-52fba5@lostmaths.uk - 2024-07-20 15:30 +0200
    Bug#1072996: /dev/mapper/ nodes being renamed Agustin Martin <agmartin@debian.org> - 2024-07-23 11:30 +0200

csiph-web