Btrfs - Revision history

Clammy-Deceiver: Added Filesystem Category

2026-01-07T14:48:37Z

Added Filesystem Category

← Older revision		Revision as of 14:48, 7 January 2026
Line 356:		Line 356:

	[[Category: Configuration]]		[[Category: Configuration]]
			[[Category:Filesystem]]

Klinger: removed Category:Filesystem (the category filesystems is part of configaration-category)

2025-12-29T13:10:51Z

removed Category:Filesystem (the category filesystems is part of configaration-category)

← Older revision		Revision as of 13:10, 29 December 2025
Line 356:		Line 356:

	[[Category: Configuration]]		[[Category: Configuration]]
	~~[[Category:Filesystem]]~~

Pigeon: Polish text in /Top-level vs nested subvolumes/

2025-06-10T14:14:15Z

Polish text in Top-level vs nested subvolumes

← Older revision		Revision as of 14:14, 10 June 2025
Line 181:		Line 181:
	</syntaxhighlight>		</syntaxhighlight>

	=== Top level vs nested subvolumes ===		=== Top-level vs nested subvolumes ===

	In btrfs, subvolumes can be created either at the top level of the filesystem or within other subvolumes		In btrfs, subvolumes can be created either at the top level of the filesystem or within other subvolumes.

	* Top level subvolumes are created directly under the filesystem's root. By default, the root volume id is 5. Top level subvolumes are easier to ~~snapshotted~~, ~~rolled~~ back or ~~destroyed~~ independently. This is good for things such as <code>/home</code> or <code>/nix</code>.		* Top-level subvolumes are created directly under the filesystem's root. By default, the root volume ID is 5. Top-level subvolumes are easier to snapshot, roll back or destroy independently. This is good for things such as <code>/home</code> or <code>/nix</code>.

	* Nested subvolumes are created inside an existing subvolume or directory within the filesystem. All nested subvolumes inherit the mount status of their parent unless mounted ~~seperately~~. This layout is useful for organizing related subvolumes under a common namespace. For example, a top-level subvolume such as <code>/srv/nfs</code> can contain multiple nested subvolumes like <code>/srv/nfs/export1</code> and <code>/srv/nfs/export2</code>.		* Nested subvolumes are created inside an existing subvolume or directory within the filesystem. All nested subvolumes inherit the mount status of their parent unless mounted separately. This layout is useful for organizing related subvolumes under a common namespace. For example, a top-level subvolume such as <code>/srv/nfs</code> can contain multiple nested subvolumes like <code>/srv/nfs/export1</code> and <code>/srv/nfs/export2</code>.

Pigeon: /Deduplication/: mention useful upstream wiki page

2025-06-10T13:43:58Z

Deduplication: : mention useful upstream wiki page

← Older revision		Revision as of 13:43, 10 June 2025
Line 142:		Line 142:

	== Deduplication ==		== Deduplication ==
			Files with (partially) equal contents can be deduplicated using [https://github.com/Zygo/bees bees] or [https://github.com/markfasheh/duperemove duperemove]. The [https://btrfs.readthedocs.io/en/latest/Deduplication.html upstream wiki entry] on deduplication provides an overview of available features of these programs.
	Files with (partially) equal contents can be deduplicated using [https://github.com/Zygo/bees bees] or [https://github.com/markfasheh/duperemove duperemove].

	bees can be configured in <code>configuration.nix</code>:		bees can be configured in <code>configuration.nix</code>:

Pigs: Include trim support section

2025-06-08T05:48:27Z

Include trim support section

← Older revision		Revision as of 05:48, 8 June 2025
Line 349:		Line 349:
	btrfs subvolume delete /btrfs/ext2_saved		btrfs subvolume delete /btrfs/ext2_saved
	</syntaxhighlight>		</syntaxhighlight>

			=== TRIM support ===

			{{main\|Filesystems#SSD TRIM support}}

			Refer to [https://btrfs.readthedocs.io/en/latest/Trim.html btrfs docs] on how Trim works with btrfs through the <code>discard</code> mount option.

	[[Category: Configuration]]		[[Category: Configuration]]
	[[Category:Filesystem]]		[[Category:Filesystem]]

DoggoBit: Change warning notice

2025-06-04T22:49:33Z

Change warning notice

← Older revision		Revision as of 22:49, 4 June 2025
Line 326:		Line 326:
	== Convert Ext3/Ext4 system partition to Btrfs ==		== Convert Ext3/Ext4 system partition to Btrfs ==

	~~<div style="border: 1px solid var(--border-color-error); background: var(--background-color-error-subtle); padding: 30px; border-radius: 5px; margin: 10px 0px; display: flex; align-items: center;">~~		{{Warning\|Note that migrating your existing root filesystem can cause data loss or make your system unbootable. Make sure to backup the partition or your files. Proceed only if you know what you're doing!}}
	~~<div style="color: var(--border-color-error); font-size: 40px; margin-right: 15px; background: var(--background-color-error-subtle); display: flex; line-height: 0; align-items: center;">⚠</div>~~
	~~<div style="color: var(--border-color-error); font-size: 15px; font-style: normal; font-weight: 400; line-height: normal; text-align: left;">~~Note that migrating your existing root filesystem can cause data loss or make your system unbootable. Make sure to backup the partition or your files. Proceed only if you know what you're doing!~~</div>~~
	~~</div>~~

	To convert the existing filesystem (Ext3/4) to Btrfs, boot into a NixOS live system and run the following commandː<syntaxhighlight lang="sh">		To convert the existing filesystem (Ext3/4) to Btrfs, boot into a NixOS live system and run the following commandː<syntaxhighlight lang="sh">

Klinger: /* Tips and tricks */ Link to Btrbk

2025-04-30T19:12:36Z

Tips and tricks: Link to Btrbk

← Older revision		Revision as of 19:12, 30 April 2025
Line 240:		Line 240:

	= Tips and tricks =		= Tips and tricks =

			== Backup ==

			[[Btrbk]] is a tool for creating snapshots and remote backups of btrfs subvolumes.

	== Installation with encryption ==		== Installation with encryption ==

Pigs: Fleshed out the usage section, discussed top level vs nested subvolumes

2025-04-27T05:53:47Z

Fleshed out the usage section, discussed top level vs nested subvolumes

← Older revision		Revision as of 05:53, 27 April 2025
Line 3:		Line 3:
	{{note\| Use [https://github.com/nix-community/disko/ disko] to manage your NixOS storage layout declaratively. The following shows a manual approach as seen in traditional Linux distributions.}}		{{note\| Use [https://github.com/nix-community/disko/ disko] to manage your NixOS storage layout declaratively. The following shows a manual approach as seen in traditional Linux distributions.}}

	= Installation =		= Installation of NixOS on btrfs =

	{{note\|The following example is for EFI enabled systems. Adjust commands accordingly for a BIOS installation.}}		{{note\|The following example is for EFI enabled systems. Adjust commands accordingly for a BIOS installation.}}
Line 164:		Line 164:
	== Subvolumes ==		== Subvolumes ==

	~~Create~~ a subvolume		To display all subvolumes within a mounted btrfs filesystem:

			<syntaxhighlight lang="bash">
			btrfs subvolume list -t /mnt
			</syntaxhighlight>

			To create a new subvolume at a specified location:

	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
Line 170:		Line 176:
	</syntaxhighlight>		</syntaxhighlight>

	~~Remove a~~ subvolume		To remove an existing subvolume:

	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	btrfs subvolume delete /mnt/nixos		btrfs subvolume delete /mnt/nixos
	</syntaxhighlight>		</syntaxhighlight>

			=== Top level vs nested subvolumes ===

			In btrfs, subvolumes can be created either at the top level of the filesystem or within other subvolumes

			* Top level subvolumes are created directly under the filesystem's root. By default, the root volume id is 5. Top level subvolumes are easier to snapshotted, rolled back or destroyed independently. This is good for things such as <code>/home</code> or <code>/nix</code>.

			* Nested subvolumes are created inside an existing subvolume or directory within the filesystem. All nested subvolumes inherit the mount status of their parent unless mounted seperately. This layout is useful for organizing related subvolumes under a common namespace. For example, a top-level subvolume such as <code>/srv/nfs</code> can contain multiple nested subvolumes like <code>/srv/nfs/export1</code> and <code>/srv/nfs/export2</code>.



	== Snapshots ==		== Snapshots ==

Arch is the best: /* Transfer snapshot */Add --compressed-data trick

2025-04-27T00:35:59Z

Transfer snapshot: Add --compressed-data trick

← Older revision		Revision as of 00:35, 27 April 2025
Line 220:		Line 220:
	sudo btrfs send /snapshots/nixos_snapshot_202302 \| zstd \| ssh root@192.168.178.110 'zstd -d \| btrfs receive /mnt/nixos'		sudo btrfs send /snapshots/nixos_snapshot_202302 \| zstd \| ssh root@192.168.178.110 'zstd -d \| btrfs receive /mnt/nixos'
	</syntaxhighlight>		</syntaxhighlight>

			If both the sender and receiver side have Btrfs with the same compression algorithm and level, you can instead use <code>send --compressed-data</code> to avoid decompressing and recompressing the data.

	= Tips and tricks =		= Tips and tricks =

Pigs: Fix section headers, update swap file section to let nixos handle swap file creating

2025-04-22T05:11:15Z

Fix section headers, update swap file section to let nixos handle swap file creating

Show changes