From: David Sterba <dsterba@suse.cz>
To: Ken D'Ambrosio <ken@jots.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs default on Fedora?
Date: Mon, 13 Jul 2020 11:32:37 +0200 [thread overview]
Message-ID: <20200713093237.GD3703@twin.jikos.cz> (raw)
In-Reply-To: <933824829995390cef16f757cab1ddbc@jots.org>
On Sat, Jul 11, 2020 at 02:38:26PM -0400, Ken D'Ambrosio wrote:
> Hi! I just saw this mentioned on a BBS I'm on:
> https://fedoraproject.org/wiki/Changes/BtrfsByDefault
>
> I'll admit, I'm incredibly surprised, and pleased, to see that this
> might happen. I do have three items of concern as Joe End User. (Do
> note that for home use (where I use btrfs) I'm usually on Ubuntu or a
> variant and not RH, if that matters.)
>
> * Swap files. At least last time I checked, it was a PITA to take a
> snapshot of a volume that had a swapfile on it -- I wound up writing a
> wrapper that goes, does a swapoff, removes the file, creates the
> snapshot, and then re-creates the file. Is this still "a thing"? Or
> is there a way to work around that that isn't kludgey?
The workaround is to use separate subvolume for swapfile. Anything else
would cause only problems. Imagine you have a swapfile on root
partition, take frequent snapshots. As the swapfile contents change
during system use, the shared blocks get unshared and occupy more space.
In the end, each rootfs snapshot could have it's own swapfile with
useless data.
Requiring the separate subvolume was a compromise, it's not ideal but
IMHO at least makes things clear. Deleting a swapfile will release the
blocks, there's only one instance of the swapfile (for swapon/swapoff).
prev parent reply other threads:[~2020-07-13 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 18:38 Btrfs default on Fedora? Ken D'Ambrosio
2020-07-11 21:18 ` Chris Murphy
2020-07-12 5:28 ` Andrei Borzenkov
2020-07-13 9:13 ` David Sterba
2020-07-13 9:32 ` David Sterba [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200713093237.GD3703@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=ken@jots.org \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox