Is zram0 governed by a file system? #3193
-
|
Hello. Here the zram0 partition shows no file system associated with it. Here it is not referred to as a file system. So should we deduce that zram0 is not governed by a file system? Or could this be an omission in lsblk, therefore the file system would be Linux swap file in version 1? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
By default, lsblk reads data from udevd. However, udevd does not collect file system-related information from zrams. This can be seen in the output of According to the rules in https://github.com/systemd/systemd/blob/main/rules.d/60-persistent-storage.rules.in, zram is not included in the list of allowed devices for KERNEL!=. In the current git tree, lsblk can be forced to read data directly from the device using libblkid. In this case, all properties are retrieved. We need to report it to systemd (udev) guys. |
Beta Was this translation helpful? Give feedback.
-
|
Sent systemd PR: systemd/systemd#34361 |
Beta Was this translation helpful? Give feedback.
By default, lsblk reads data from udevd. However, udevd does not collect file system-related information from zrams. This can be seen in the output of
udevadm info --export /dev/zram0, where there are no ID_FS_* variables present.According to the rules in https://github.com/systemd/systemd/blob/main/rules.d/60-persistent-storage.rules.in, zram is not included in the list of allowed devices for KERNEL!=.
In the current git tree, lsblk can be forced to read data directly from the device using libblkid. In this case, all properties are retrieved.