(Vivid) zram-config 0.3 Job for zram-config.service failed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Vivid |
Invalid
|
Undecided
|
Unassigned | ||
zram-config (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Vivid |
Fix Released
|
High
|
Unassigned |
Bug Description
[Impact]
* People using some non English locale, zram devices are not loaded
* The service fails to stop and unloading zram module as well
//who wrote this? The impact is probably for all languages including English. The new version works : provided zram module is blacklisted to avoid being loaded during boot! See my next comment which will be #13.
Thanks, Mélodie
[Test Case]
* Install the new zram-config package
* Reboot and check that the zram devices are created:
$ swapon -s
-> returns some zram devices
* $ sudo systemctl status -l zram-config.service
-> no error
* Stop the service:
$ sudo systemctl stop zram-config.service
* $ sudo systemctl status -l zram-config.service
-> no error
* swapon -s
-> no more zram device listed
[Regression Potential]
* Services loading change may impact English-local user. However, the fix has already been confirmed to be working on wily.
* Stopping the service was already failing on unloading the module, so no additional regression is possible there.
-------
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.
$
When invoking the suggested commands:
****
$ LANG=C systemctl status zram-config.service -l
* zram-config.service - Initializes zram swaping
Loaded: loaded (/lib/systemd/
Active: failed (Result: exit-code) since Tue 2015-04-28 19:34:37 CEST; 2min 7s ago
Process: 744 ExecStart=
Main PID: 744 (code=exited, status=255)
Apr 28 19:34:37 bento64 init-zram-
Apr 28 19:34:37 bento64 init-zram-
Apr 28 19:34:37 bento64 init-zram-
Apr 28 19:34:37 bento64 init-zram-
Apr 28 19:34:37 bento64 init-zram-
Apr 28 19:34:37 bento64 init-zram-
Apr 28 19:34:37 bento64 systemd[1]: zram-config.
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
Apr 28 19:34:37 bento64 init-zram-
Apr 28 19:34:37 bento64 kernel: zram: Cannot change disksize for initialized device
Apr 28 19:34:37 bento64 init-zram-
Apr 28 19:34:37 bento64 init-zram-
Apr 28 19:34:37 bento64 init-zram-
Apr 28 19:34:37 bento64 init-zram-
Apr 28 19:34:37 bento64 init-zram-
Apr 28 19:34:37 bento64 systemd[1]: zram-config.
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://
--
-- 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(
Apr 28 19:34:37 bento64 audit[781]: <audit-1107> pid=781 uid=102 auid=4294967295 ses=4294967295 msg='apparmo
Apr 28 19:34:37 bento64 kernel: audit: type=1107 audit(143024247
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/
rmmod: ERROR: unexpected getopt_long() value 'w'.
$ cat /proc/swaps
Filename Type Size Used Priority
$
$ LANG=C sudo /usr/bin/
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/
/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
description: | updated |
tags: |
added: verification-done removed: verification-needed |
Hi,
I think the bug #1448530 is not related, this is why:
I am using Vivid in French and one zram block device is created:
$ cat /proc/swaps
Filename Type Size Used Priority
/dev/zram0 partition 947216 0 100
/dev/sda5 partition 4607996 0 -1
$
We can say it works, partially.