On Tue, Apr 22, 2014 at 9:05 AM, Reindl Harald <h.reindl@xxxxxxxxxxxxx> wrote: > Am 22.04.2014 15:00, schrieb Josh Boyer: >> On Tue, Apr 22, 2014 at 8:58 AM, Reindl Harald <h.reindl@xxxxxxxxxxxxx> wrote: >>> >>> Am 22.04.2014 14:55, schrieb Josh Boyer: >>>> On Tue, Apr 22, 2014 at 8:46 AM, Reindl Harald <h.reindl@xxxxxxxxxxxxx> 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 What loaded it? It doesn't autoload. > 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 I have a rawhide VM here too, it has nothing related to zram configuration, and the module isn't loaded. Every machine I have is like this. [jwboyer@localhost ~]$ lsmod | grep zram [jwboyer@localhost ~]$ dmesg | grep zram [jwboyer@localhost ~]$ ls /dev/zram* ls: cannot access /dev/zram*: No such file or directory [jwboyer@localhost ~]$ uname -a Linux localhost.localdomain 3.15.0-0.rc2.git0.1.fc21.x86_64 #1 SMP Mon Apr 21 08:55:13 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux [jwboyer@localhost ~]$ modinfo zram filename: /lib/modules/3.15.0-0.rc2.git0.1.fc21.x86_64/kernel/drivers/block/zram/zram.ko description: Compressed RAM Block Device author: Nitin Gupta <ngupta@xxxxxxxxxx> license: Dual BSD/GPL depends: intree: Y vermagic: 3.15.0-0.rc2.git0.1.fc21.x86_64 SMP mod_unload signer: Fedora kernel signing key sig_key: A4:E8:3E:17:78:1D:AE:9F:50:BF:F1:AA:78:FE:F3:13:D1:37:22:D7 sig_hashalgo: sha256 parm: num_devices:Number of zram devices (uint) [jwboyer@localhost ~]$ [jwboyer@localhost ~]$ rpm -q systemd systemd-212-1.fc21.x86_64 [jwboyer@localhost ~]$ So, I guess you need to figure out what loaded the zram module. josh _______________________________________________ kernel mailing list kernel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/kernel
