[Bug 1449678] Re: zram-config 0.3 : Job for zram-config.service failed
Mélodie
meets at gmx.fr
Sun Jun 14 12:23:07 UTC 2015
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
Foundations Bugs, which is subscribed to zram-config in Ubuntu.
https://bugs.launchpad.net/bugs/1449678
Title:
(Vivid) zram-config 0.3 Job for zram-config.service failed
Status in zram-config package in Ubuntu:
New
Bug description:
Hi,
While testing how zram-config is going in Ubuntu Vivid, I meet with
error while doing restart and or stop/start.
It seems to stop fine but throws an error when starting again or
performing a restart.
I have installed zram-config 0.3 just today and haven't rebooted yet.
The CPU is "AMD Athlon(tm) II X2 260 Processor"
As stated in bug #1449665 there is one block device created:
$ cat /proc/swaps
Filename Type Size Used Priority
/dev/zram0 partition 947216 0 5
$
Here:
$ sudo systemctl stop zram-config
$ cat /proc/swaps
Filename Type Size Used Priority
/dev/zram0 partition 947216 0 5
$
after the stop, the prompt is back without error, but it has done
nothing.
With restart:
$ sudo systemctl restart zram-config
Job for zram-config.service failed. See "systemctl status zram-config.service" and "journalctl -xe" for details.
$
When invoking the suggested commands:
****
$ LANG=C systemctl status zram-config.service -l
* zram-config.service - Initializes zram swaping
Loaded: loaded (/lib/systemd/system/zram-config.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2015-04-28 19:34:37 CEST; 2min 7s ago
Process: 744 ExecStart=/usr/bin/init-zram-swapping (code=exited, status=255)
Main PID: 744 (code=exited, status=255)
Apr 28 19:34:37 bento64 init-zram-swapping[744]: sh: echo: I/O error
Apr 28 19:34:37 bento64 init-zram-swapping[744]: mkswap: error: /dev/zram0 is mounted; will not make swapspace
Apr 28 19:34:37 bento64 init-zram-swapping[744]: swapon: /dev/zram0 : échec de swapon: Périphérique ou ressource occupé
Apr 28 19:34:37 bento64 init-zram-swapping[744]: /usr/bin/init-zram-swapping: 21: /usr/bin/init-zram-swapping: cannot create /sys/block/zram1/disksize: Directory nonexistent
Apr 28 19:34:37 bento64 init-zram-swapping[744]: /dev/zram1: Aucun fichier ou dossier de ce type
Apr 28 19:34:37 bento64 init-zram-swapping[744]: swapon: stat failed /dev/zram1: Aucun fichier ou dossier de ce type
Apr 28 19:34:37 bento64 systemd[1]: zram-config.service: main process exited, code=exited, status=255/n/a
Apr 28 19:34:37 bento64 systemd[1]: Failed to start Initializes zram swaping.
Apr 28 19:34:37 bento64 systemd[1]: Unit zram-config.service entered failed state.
Apr 28 19:34:37 bento64 systemd[1]: zram-config.service failed.
$
****
****
-- Unit zram-config.service has begun starting up.
Apr 28 19:34:37 bento64 audit[781]: <audit-1107> pid=781 uid=102 auid=4294967295 ses=4294967295 msg='apparmo
exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?'
Apr 28 19:34:37 bento64 init-zram-swapping[744]: sh: echo: I/O error
Apr 28 19:34:37 bento64 kernel: zram: Cannot change disksize for initialized device
Apr 28 19:34:37 bento64 init-zram-swapping[744]: mkswap: error: /dev/zram0 is mounted; will not make swapspa
Apr 28 19:34:37 bento64 init-zram-swapping[744]: swapon: /dev/zram0<C2><A0>: <C3><A9>chec de swapon: P<C3>
Apr 28 19:34:37 bento64 init-zram-swapping[744]: /usr/bin/init-zram-swapping: 21: /usr/bin/init-zram-swappin
Apr 28 19:34:37 bento64 init-zram-swapping[744]: /dev/zram1: Aucun fichier ou dossier de ce type
Apr 28 19:34:37 bento64 init-zram-swapping[744]: swapon: stat failed /dev/zram1: Aucun fichier ou dossier de
Apr 28 19:34:37 bento64 systemd[1]: zram-config.service: main process exited, code=exited, status=255/n/a
Apr 28 19:34:37 bento64 systemd[1]: Failed to start Initializes zram swaping.
-- Subject: Unit zram-config.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit zram-config.service has failed.
--
-- The result is failed.
Apr 28 19:34:37 bento64 systemd[1]: Unit zram-config.service entered failed state.
Apr 28 19:34:37 bento64 systemd[1]: zram-config.service failed.
Apr 28 19:34:37 bento64 polkitd(authority=local)[3990]: Unregistered Authentication Agent for unix-process:7
Apr 28 19:34:37 bento64 audit[781]: <audit-1107> pid=781 uid=102 auid=4294967295 ses=4294967295 msg='apparmo
exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?'
Apr 28 19:34:37 bento64 kernel: audit: type=1107 audit(1430242477.545:27): pid=781 uid=102 auid=4294967295 s
exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?'
lines 1809-1834/1834 (END)
****
I have done a test using directly the scripts created for /usr/bin,
the results seem interesting:
$ sudo /usr/bin/end-zram-swapping
rmmod: ERROR: unexpected getopt_long() value 'w'.
$ cat /proc/swaps
Filename Type Size Used Priority
$
$ LANG=C sudo /usr/bin/init-zram-swapping
sh: echo: I/O error
mkswap: error: /dev/zram0 is mounted; will not make swapspace
swapon: /dev/zram0: swapon failed: Device or resource busy
/usr/bin/init-zram-swapping: 21: /usr/bin/init-zram-swapping: cannot create /sys/block/zram1/disksize: Directory nonexistent
/dev/zram1: No such file or directory
swapon: stat failed /dev/zram1: No such file or directory
$
I hope I have tested the right way. If anything more is needed, log
files or so, please ask.
Best regards,
Mélodie
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1449678/+subscriptions
More information about the foundations-bugs
mailing list