Linux

48077 readers

771 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

nooter692@lemmy.ml

AgreeableLandscape@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Help on BTRFS setup (programming.dev)

submitted 10 months ago by actual_patience@programming.dev to c/linux@lemmy.ml

17 comments fedilink hide all child comments

I'm attempting a new install. I want to use btrfs with swapfile.

Do I need to disable compression on my swap subvolume?

Is there anything else I should keep in mind for fstab if I want to, say, not keep track of my Downloads folder when snapshotting?

Here is my fstab:

LABEL=arch@btrfs        /               btrfs           rw,relatime,discard=async,space_cache=v2,subvolid=256,subvol=>

LABEL=arch@btrfs        /home           btrfs           rw,relatime,discard=async,space_cache=v2,subvolid=257,subvol=>

LABEL=arch@btrfs        /var/cache/pacman/pkg   btrfs           rw,relatime,discard=async,space_cache=v2,subvolid=259>

LABEL=arch@btrfs        /var/log        btrfs           rw,relatime,discard=async,space_cache=v2,subvolid=258,subvol=>

LABEL=arch@btrfs        /.snapshots     btrfs           rw,relatime,discard=async,space_cache=v2,subvolid=260,subvol=>

LABEL=arch@btrfs        /swap           btrfs           rw,relatime,discard=async,space_cache=v2,subvolid=263,subvol=>

LABEL=efi@fat32         /efi            vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=asci>

/swap/swapfile          none            swap            defaults        0 0

you are viewing a single comment's thread
view the rest of the comments

[–] actual_patience@programming.dev 2 points 10 months ago (1 children)

"subvolume - cannot be snapshotted if it contains any active swapfiles"

Make a subvolume only for the swapfile.

has a chance to fragment

This is true for all files. Is it a bigger problem for swap?

has issues with hibernation (that I've personally encountered multiple times)

This one I can't refute. How long ago did you have these issues?

[–] recursive_recursion@programming.dev 3 points 10 months ago* (last edited 10 months ago) (1 children)

Make a subvolume only for the swapfile.

doesn't this kinda defeat the purpose/benefits of using a swapfile?

This is true for all files. Is it a bigger problem for swap?

specificly swapfiles yes, for swap partitions nope

How long ago did you have these issues?

Dec 2022, was still using and testing with swapfiles then and said fuck it as it caused too much problems.

I can't rule out user error till I retest and strictly "follow the guide to the T" as I made modifications while following the same Arch guide for swapfile with BTRFS

edit:
also for clarification, I'm still not sure which one is optimal/best as I initially thought that using swapfile was forward thinking for the future, I'm using and recommending swap partitions as it seems to be the easiest to implement once and use continuously without any problems atm.

[–] Supermariofan67@programming.dev 2 points 10 months ago (1 children)

The reason I use a swap file is so that I can have only one partition backed by LUKS disk encryption, rather than having to screw around with lvm which comes with its own performance overhead and all. I've personally never had issues hibernating to.it, but given how much buggy uefi firmware is out there I'm not surprised to hear that other have issues