[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#883735: marked as done (initramfs-tools: automatic resume doesn't work for lvm swap partitions)

Your message dated Thu, 07 Dec 2017 00:06:11 +0000
with message-id <1512605171.2768.70.camel@decadent.org.uk>
and subject line Re: Bug#883735: initramfs-tools: automatic resume doesn't work for lvm swap partitions
has caused the Debian Bug report #883735,
regarding initramfs-tools: automatic resume doesn't work for lvm swap partitions
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
883735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883735
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: initramfs-tools
Version: 0.130
Severity: normal

Hi,

I had noticed this bug for quite a while now, but since I rarely turn my
machine off I left investigating what the problem was until now.

Every time I boot my laptop, it prints a lot of messages like this,
before eventually giving up:

Begin: Waiting for suspend/resume device ...
Begin: Running /scripts/local-block ... done
[...]
Begin: Running /scripts/local-block ... done
Gave up waiting for suspend/resume device.

I traced this down to the swap device being on an LVM partition on my
laptop. The script which automatically determines which device to resume
from stores the blkid in the initramfs, but unfortunately the lvm2
local-block script does not know how to activate LVM partitions based on
blkid. This means the swap device is never created and the initramfs
will never be able to find it.

Is it possible (and a good idea) to store the /dev/mapper path instead
of the blkid when the swap partition is on LVM?

I managed to solve my specific issue by manually setting RESUME to the
correct /dev/mapper path.

Thanks,
James

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
On Wed, 2017-12-06 at 23:48 +0000, James Cowgill wrote:
> Package: initramfs-tools
> Version: 0.130
> Severity: normal
> 
> Hi,
> 
> I had noticed this bug for quite a while now, but since I rarely turn my
> machine off I left investigating what the problem was until now.
[...]
> Is it possible (and a good idea) to store the /dev/mapper path instead
> of the blkid when the swap partition is on LVM?
> 
> I managed to solve my specific issue by manually setting RESUME to the
> correct /dev/mapper path.

This is the correct way to refer to LVs used as root, /usr or resume
partition.  The reason for this is that lvm2 only activates VGs that
are definitely needed, and there is no way to determine whether a
filesystem UUID or label refers to an LV (or which VG it's in).

Ben.

-- 
Ben Hutchings
If the facts do not conform to your theory, they must be disposed of.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: