'Twas brillig, and jjacky at 13/10/12 13:58 did gyre and gimble:
> Forgot to say: not stopping the swap also meant that, with encrypted
> swaps, the LUKS device couldn't be detached (since it's still in use)
> and would result in errors on shutdown:
>
> systemd-cryptsetup[3327]: Failed to deactiva
Hi,
I'm having trouble debugging the problem below. Maybe somebody has an
idea... When I run journalctl, on a specific (large) set of journal
logs, it segfaults. Always in the same place.
Program terminated with signal 11, Segmentation fault.
#0 md_close (a=0x1b01930) at md.c:771
771
On Saturday 2012-10-13 13:26, Kay Sievers wrote:
>On Fri, Oct 12, 2012 at 11:50 PM, Jan Engelhardt wrote:
>> Now, in /etc/modprobe.d/99-local.conf, I have set forth:
>>
>> options loop max_loop=256 max_part=15
>
>[...] losetup has proper loop allocation code, pre-creation is not needed.
>Also lo
Forgot to say: not stopping the swap also meant that, with encrypted
swaps, the LUKS device couldn't be detached (since it's still in use)
and would result in errors on shutdown:
systemd-cryptsetup[3327]: Failed to deactivate: Invalid argument
___
system
Starting a swap unit pointing to (What) a symlink (e.g. /dev/mapper/swap
or /dev/disk/by-uuid/...) would have said unit be marked active, follow
the one using the "actual" device (/dev/{dm-1,sda3}), but that new unit
would be seen as inactive.
Since all requests to stop swap units would follow/redi
On Fri, Oct 12, 2012 at 11:50 PM, Jan Engelhardt wrote:
> on openSUSE 12.2, which has udev-182 and systemd-44, I found that
> starting udevd creates some loop devices in /dev (which is a devtmpfs).
> Now, in /etc/modprobe.d/99-local.conf, I have set forth:
>
> options loop max_loop=256 max_part
