Hi,
Many days after I have removed zram-config I still have zram loaded and
a /dev/zram0 created. This is what I did to remove it right now, and I
have not yet rebooted to see the result. If after a reboot I need to do
it all over again, I will have to blacklist it.
Please note that this situation is first seen for me, since many years.
Also note afaik some scripts done by mystillef for Fedora, which uses
systemd since a long time, don't have this issue.
****
$ cat /proc/swaps
Filename Type Size Used Priority
/dev/zram0 partition 947216 0 100
/dev/sda6 partition 4607996 0 -1
$
****
There is a zram0 device loaded (I haven't asked it to load, this is what I
found after a fresh boot), with priority 100 (which is not an issue for me,
just notice the priority if using zram-config is 5, not 100).
****
$ systemctl list-units | grep zram
sys-devices-virtual-block-zram0.device
loaded active plugged /sys/devices/virtual/block/zram0
dev-zram0.swap
loaded active active /dev/zram0
****
Information about systemd related loaded units
****
$ sudo swapoff /dev/zram0
[sudo] password for melodie:
$
****
unmounting the swap device
****
$ systemctl list-units | grep zram
sys-devices-virtual-block-zram0.device
loaded active plugged /sys/devices/virtual/block/zram0
****
Checking what units are still seen
****
$ sudo systemctl disable sys-devices-virtual-block-zram0.device
****
Disabling the above unit
****
$ systemctl list-units | grep zram
sys-devices-virtual-block-zram0.device
loaded active plugged /sys/devices/virtual/block/zram0
****
Checking the result of the disable command. Obviously it produced no result.
Maybe a rmmod will do it? See after:
****
$ sudo rmmod zram
$ sudo systemctl disable sys-devices-virtual-block-zram0.device
$ systemctl list-units | grep zram
$
****
Now it worked!
My guess is I can redo it all over again after next boot, as long as
zram isn't blacklisted in a blacklist file under /etc/
This is an issue which is very severe because it can affect the
stability of a system : for one, zram is still in the staging directory;
for two we have seen these last years that depending on the kernel and
how it was tweaked (Precise and after), using zram at same time as these
kernels could make a session freeze completely.
So, I am aware that I am using an edition not meant for the large
audience : I am a tester here and I know it. I would appreciate this
issue to be addressed within a few months and if possible, long before
the next LTS is out.
The expected behavior:
1) I install zram-config, it works a treat;
2) I remove zram-config from the installed packages, no more zram is
loaded;
3) additional options would be welcome:
* the ability to setup how large the block devices should be (1/3, or 1/4 of
available memory, or any number, as explained in the wiki of the original
compcache project);
* the ability to decide how many block devices should be created, in relation
to the number of cores ran by a machine;
*the ability to start and stop it on demand, without the need to remove it from
the system.
Best regards,
Mélodie
** Summary changed:
- zram-config 0.3 : Job for zram-config.service failed
+ (Vivid) zram-config 0.3 Job for zram-config.service failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1449678
Title:
(Vivid) zram-config 0.3 Job for zram-config.service failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1449678/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
