Control: reassign -1 src:linux
Control: severity -1 normal
Control: tag -1 moreinfo

On Wed, 31 May 2017, Garjola Dindi wrote:
> I am using Debian Stretch on a laptop with a HDD (/dev/sda) and an SSD
> (/dev/sdd). My swap and home partitions are encrypted with lvm. The
> ouput of lsblk is:
> 
> NAME                          MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
> sda                             8:0    0 931.5G  0 disk  
> ├─sda1                          8:1    0   243M  0 part  /boot
> ├─sda2                          8:2    0     1K  0 part  
> └─sda5                          8:5    0 931.3G  0 part  
>   └─sda5_crypt                254:0    0 931.3G  0 crypt 
>     ├─pc--117--162--vg-root   254:1    0 893.6G  0 lvm   /home
>     └─pc--117--162--vg-swap_1 254:2    0  37.7G  0 lvm   [SWAP]
> sdb                             8:16   0   477G  0 disk  
> └─sdb1                          8:17   0   477G  0 part  /
> 
> For several weeks now I have been having issues after resume (both
> from RAM or from disk): my /home seems not to be accessible (at least
> for writing). This does not happen every time, but more something like
> once every 10 or 20 resume cycles.
> 
> At first, I thought this was related to an initramfs-tools (0.129)
> update where it was mentioned that the RESUME variable had to be set
> in the configuration, but this should only affect resuming from disk.
> I however tried to set this to different values (the /dev/XXX, auto,
> none) but nothing changes with my issue.
> 
> Since I also have a warning at boot time saying "Failing to connect to
> lvmetad" I set use_lvmetad = 0 in /etc/lvm/lvm.conf. Again, nothing
> changes.

You've filed this bug against bugs.debian.org which is the pseudopackage
for reporting bugs which affect the bug tracking system itself, not for
bugs which the underlying package is unclear.

I've reassigned it to the linux source package, but you'll need to
provide more information before the maintainers of that package will be
able to help.

In this particular case, I'm suspecting that /home or possibly swap is
getting mounted read only, but the output of dmesg; when you have a
failure will provide more information. [Along with the precise kernel
version and whether this happens on newer kernels (4.11.0-trunk is in
experimental) too.]



-- 
Don Armstrong                      https://www.donarmstrong.com

"In my many years I have come to a conclusion that one useless man is
a shame, two is a law firm, and three or more is a congress."
 -- John Adams

Reply via email to