On Thu, 06 Oct 2016 at 22:12:28 +0200, Guilhem Moulin wrote:
> Looking at the hook script's diff since 1.7.0-2 it's unclear to me
> what now causes the warning to appear.
For the record, this is because up to 2:1.7.0-1 get_fs_devices() used to
prefix the list of underlying devices with a space " "
On Fri, 07 Oct 2016 at 11:55:35 +0200, Paride Legovini wrote:
> but I'm not sure of what happens when several devices contain a
> filesystem with the same UUID. I guess this is the reason for using
> devids instead of the uuid. In the case of multiple devices the output
> of btrfs filesystem show i
On 2016-10-07 11:30, Guilhem Moulin wrote:
>> Perhaps we should add a --no-simplify to that loop?
>
> Hmm but we'll still want unambiguous crypttab(5) lookups. It's
> unfortunate that `btrfs filesystem` lists /dev/sda2 while the FS
> actually uses device UUIDs internally. I think we need to call
On Fri, 07 Oct 2016 at 10:15:55 +0200, Paride Legovini wrote:
> $(canonical_device "$device" --no-simplify) resolves the UUID entry to
> /dev/sda2, then btrfs is asked to show the list of devices relevant for
> the filesystem contained in that device. (btrfs filesystems can span on
> several device
OK, I think the problem happens with with btrfs specifically. In
get_fs_devices() we have this loop (cryptroot:32):
https://paste.debian.net/858017/
In line 5:
$(canonical_device "$device" --no-simplify) resolves the UUID entry to
/dev/sda2, then btrfs is asked to show the list of devices releva
On 2016-10-06 22:12, Guilhem Moulin wrote:
> On Thu, 06 Oct 2016 at 19:42:55 +0200, Paride Legovini wrote:
>> cryptsetup: WARNING: failed to detect canonical device of /dev/sda2
>
> For the record, the hook script gives this warning as it doesn't know
> whether the device is to be unlocked at init
On Thu, 06 Oct 2016 at 19:42:55 +0200, Paride Legovini wrote:
> cryptsetup: WARNING: failed to detect canonical device of /dev/sda2
For the record, the hook script gives this warning as it doesn't know
whether the device is to be unlocked at initramfs stage or not.
(Depending on what's on the devi
Package: cryptsetup
Version: 2:1.7.2-2
Followup-For: Bug #784881
The warning is now doubled:
cryptsetup: WARNING: failed to detect canonical device of /dev/sda2
cryptsetup: WARNING: could not determine root device from /etc/fstab
On this system /dev/sda2 is a btrfs filesystem mounted on / using
I confirm that issue is present, I've been getting that warning for
years, even on separate clean installs on different machines that I
always keep up to date.
Seems harmless, but for sure it's annoying.
Paride
Package: cryptsetup
Version: 2:1.6.6-5
Severity: normal
Hi, maintainers
I got this warning while updating initramfs, pleas take a look, thanks.
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
cryptsetup: WARNING: failed to detect canonical device of /dev/s
10 matches
Mail list logo
