On Wed, Dec 9, 2020 at 5:31 AM Chris Murphy <li...@colorremedies.com> wrote:

> I referred you to man 5 btrfs about a list of limitations of swapfiles
> on btrfs 10 days ago.
>
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/XF7YO27N2XPWGLPMPUN76VFT3RW2KFYS/


Apologies, I missed that.


> However, it might be better to have a "swap" subvolume along with
> "root" and "home" in the top-level of the file system. And add it to
> fstab or maybe we can create a native systemd mount unit. Importantly
> we have to have complete certainty that this mount happens before
> swapon, or it'll fail. So we can't have races either. Now both issues
> are fixed. It won't be snapshot if we snapshot "root". But if we
> rollback a "root" snapshot, then the same "swap" subvolume always
> mounts into the proper position at /var/swap with the same swapfile.
>
>
Ok, how can I guarantee that the swap subvolume will be mounted before
swapon is executed ?

Is swapon executed after all mounts in /etc/fstab by design ?

Is there something else I can do to guarantee this?

Or is there no way to guarantee this now ?


Yes you were right. I have just restored my snapshot and now swap is
malfunctioning.

I guess that's because the physical offset of the file is different.

But that automatic solution is also kinda hidden. So no matter what
> there's some kind of tradeoff. And that's the long answer for why it's
> not the default yet, and also not even documented how to do a
> post-install setup of swap. But it's on my todo.
>

 Lets hope you get around to it soon.

-- 
Regards,
Sreyan Chakravarty
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

Reply via email to