Am 22.04.2014 15:00, schrieb Josh Boyer:
On Tue, Apr 22, 2014 at 8:58 AM, Reindl Harald
<h.reindl(a)thelounge.net> wrote:
>
> Am 22.04.2014 14:55, schrieb Josh Boyer:
>> On Tue, Apr 22, 2014 at 8:46 AM, Reindl Harald <h.reindl(a)thelounge.net>
wrote:
>>> interesting, i have that behavior on a Rawhide VM
>>> with no services except sshd which explains the
>>> systemd device-unit from my mail some time ago
>>
>> Yeah, you answered your own question on that thread, so I didn't look
>> into it. Reading back, it seems you installed some zram-1.0.0 RPM
>> that isn't in the Fedora repos. That seems to be what is providing
>> all the various zram related items in your VM, because zram.service
>> doesn't exist anywhere else
>
> i linked in that thread the src.rpm
Yes...
> the script with the rmmod ist part of that service and the rmmod
> with error supression is there because the virgin VM where i
> figured out how to use zram had the module unconditional loaded
OK. So it seems you found the area that is causing your issues, and
it's that script/RPM. Glad you cleared it up
*no* the other way round
/sys/devices/virtual/block/zram exists *because* zram was loaded
and that triggers sys-devices-virtual-block-zram0.device
after blacklist zram /sys/devices/virtual/block/zram exists
as well as the device-unit don't exist
a virgin rawhide VM with not anything zram related configured
or installed has the zram module loaded - that fact was in my
way by "develop" that service and RPM
https://lists.fedoraproject.org/pipermail/kernel/2014-March/005127.html
[root at rawhide ~]# systemctl list-units | grep zram
sys-devices-virtual-block-zram0.device loaded active plugged
/sys/devices/virtual/block/zram