On Fri, Dec 11, 2020 at 12:32 AM Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > > If the journal doesn't have more information about why it says this, > and if the error is reported in the journal by systemd-logind, enable > debug logging for logind and reproduce and the try to figure out why > logind is complaining: > > https://github.com/systemd/systemd/issues/15354#issuecomment-610385478 > Yes. I have finally found out the reason why logind is complaining, thanks to you. Dec 11 18:45:05 localhost.HPNotebook systemd-logind[1222]: Failed to open swap file /var/swap/fedora.swap to determine on-disk offset: Permission denied Dec 11 18:45:05 localhost.HPNotebook systemd-logind[1222]: Sent message type=method_return sender=n/a destination=:1.57 path=n/a interface=n/a member=n/a cookie=130 reply_cookie=49 signature=s error-name=n/a error-message=n/a Dec 11 18:45:05 localhost.HPNotebook systemd-logind[1222]: Got message type=method_call sender=:1.57 destination=org.freedesktop.login1 path=/org/freedesktop/login1 interface=org.freedesktop.login1.Manager member=CanHybridSleep cookie=50 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a Dec 11 18:45:05 localhost.HPNotebook systemd-logind[1222]: Sleep mode "disk" is supported by the kernel. Dec 11 18:45:05 localhost.HPNotebook systemd-logind[1222]: /dev/zram0: ignoring zram swap My permissions are as follows: Permissions of /var/swap directory: drwxr-xr-x. 1 root root 22 Dec 11 15:06 swap Permissions of the actual swap file: -rw-------. 1 root root 9663676416 Dec 11 15:09 fedora.swap Permissions of the swap subvolume: drwxr-xr-x. 1 root root 22 Dec 11 15:06 swap Mount options: UUID=7d9dbe1b-dea6-4141-807b-026325123ad8 /var/swap btrfs subvol=swap,rw,noattime,nosuid,x-systemd.device-timeout=0 0 0 /var/swap/fedora.swap none swap defaults,x-systemd.requires-mounts-for=/var/swap 0 2 Output of /proc/swaps: Filename Type Size Used Priority /dev/zram0 partition 4020220 0 100 /var/swap/fedora.swap file 9437180 0 -2 The only reason I can fathom is that systemd-logind is unable to access the directory /var/swap. IIRC, you were the one who suggested I mount in that directory. Not blaming you, but the question is what do I do now ? The bug that you have linked to is about /home not /var. So where should I keep the swap for logind to access it without any problems ? > There is a possibility there isn't enough contiguous space in the > swapfile for the hibernation image. i.e. when you fallocate the > swapfile, it may be comprised of one or even dozens of separate > extents and if one of them isn't big enough for hibernation entry then > it'll always fail. > > As far as I'm aware there isn't a way to ask fallocate for a minimum > extent size. I've sometimes had to fallocate multiple files in a row > to get a swapfile with few fragments and then delete the rest. > I don't think that is possible since the file was created with dd, not fallocate. Also the +C attribute was used. > OK you're confused. You do not need both chattr +C on the file and the > nodatacow option. You only need one of those. You should realize that > the nodatacow option applies file system wide. It's non-obvious but > really only the VFS mount options can apply separately to bind mounts. > And on Fedora, since subvolumes are mounted to specific mounts points > and are thus effectively bind mounts behind the scenes, it seems like > you can apply some mount options to specific subvolumes as if they are > separate file systems. But that's not what's going on, they're just > bind mounts. So you can do atime for one mount point, noatime for > another. And same for ro or rw. Those are VFS options. The Btrfs mount > options apply file system wide, that includes nodatacow, compress, and > so on. > > Further problem now that you're using nodatacow is that you have a > bunch of nodatacow files that have been created in the meantime. And > those do *not* have chattr +C so you have no easy way to find them. > You'd have to parse 'btrfs inspect-internal dump-tree' for the > nodatacow flag. > > nodatacow files are also no compression and no data checksums. So I'm > betting this is not what you want. Yes, I have removed the nodatacow option from my mount in fstab as it clearly had no effect. I am now using the +C attribute. -- Regards, Sreyan Chakravarty _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
