Hi.

(I'm not subscribed to the MLs, so I'm sorry in advance for responding
to everyone with so many CCs... I'm not sure Kix's message was worth it,
as the BTS was maybe enough for the moment IMHO... still, as many people
are probably busy on the same issues, let's hope this helps a bit anyway).

Rodolfo García Peñas <k...@debian.org> writes:

> 1. First, there is a problem with the typo in the initramfs-tools
> package.

I've merged #725275 to #724554, as I believe these 2 were redundant,
spotting a typo on blikd/blkid.

>
> 2. Second, if we solve the problem with the typo, and we use LVM2
> (like your system), the system won't boot. In this case is because the
> LVM2 scripts cannot check if the filesystem in format UUID= is the
> swap in a LVM volume. So, the problem is in the initramfs-tools lvm2
> script, because is unable to know it. This problem was created by the
> latest version of uswsusp package, because it use now UUID devices (no
> /dev devices), but the problem should be solved in lvm2, because is
> unable to handle UUID devices. This problem is the bug number #678687
> in lvm2. IMO, this bug should be forwareded/merged with #678687 when
> the problem with the typo will be solved. So, I don't have problems to
> hold the bug in uswsusp package if the initramfs-tools package is
> updated soon, and then forward it to lvm2.
>

It seems to me that the discussion in #724554 tends to indicate that
there are some issues with UUID for identifying LVM2 swap partitions as
resume devices, which may need to be considered before flagging #678687
as the only issue left, about the problems initially reported in #724275
(attention: almost identical numbers for tickets #725275 and #724275).

> So, the next step is try to make a patch for lvm2 package to handle
> UUID devices.
>
> This problem is critical, because the system don't boot if uswsusp is
> installed, but uswsusp is ok.
>
> Olivier, do you agree?
>

#678687 is probably an interesting problem on its own, but AFAIU it may
only be a problem for hibernation if one uses uswsusp.

>From a user standpoint, as uswsusp seems not (no longer ?) needed for
basic hibernation to work, (at least on some architectures ?), so I'd
first try to make sure everything works as expected *without* uswsusp
installed, for users of swap on LVM2, and once this is OK, proceed with
the necessary uswsusp alignments.

Kix, I appreciate your help and willingness to push for a quick solution
to #724275, but I think the wisest path for the moment (as far as
testing is concerned) seems to wait for an updated initramfs-tools, test
again boot + hibernation, without uswsusp, and then, maybe reinstall
uswsusp afterwards to see if everything works again also.

Btw, people, https://wiki.debian.org/Hibernation needs more love, IMHO.

I hope this makes sense, but I may have overlooked other important
details, as I'm not really qualified WRT initrd.

Best regards,
-- 
Olivier BERGER 
http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingenieur Recherche - Dept INF
Institut Mines-Telecom, Telecom SudParis, Evry (France)


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87bo23ixgn....@inf-8660.int-evry.fr

Reply via email to