Difference between revisions of "Talk:Btrfs"

From ArchWiki
Jump to: navigation, search
(cp --reflink and the actual meaning of CoW: Re: Thanks for fixing the section)
 
(93 intermediate revisions by 23 users not shown)
Line 1: Line 1:
== Comment about stability ==
+
{{Note|The name of the file system does not seem to have an official capitalization, so the rule for the ArchWiki has been arbitrarily set to use "Btrfs" (capital "B" and the rest lower-case); "btrfs" and "BTRFS" are therefore wrong spellings in this wiki. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 09:36, 6 January 2014 (UTC)}}
Btrfs is still under heavy development; it might be useful if someone familiar with btrfs were to add a section commenting on its overall stability. [[User:Vikingurinn|Vikingurinn]] ([[User talk:Vikingurinn|talk]]) 16:52, 17 December 2012 (UTC)
 
  
== Troubleshooting is now outdated ==
+
== "Displaying used/free space" needs rewrite ==
Would be great of some early adopters would modernize this section now that the stable release of btrfs-progs has hit [testing].  As the warning says, the package now includes the btrfsfsck which can fix problems on the filesystem!
 
  
[[User:Graysky|Graysky]] 19:27, 28 March 2012 (EDT)
+
Section "Displaying used/free space" needs a rewrite. I will hopefully do that when I have time.
 +
* The example with /usr/bin/df is misleading (on simple setups it's reporting disk usage ('used' value) quite accurate).
 +
* "btrfs filesystem usage" should be mentioned on top
 +
* there should be a link to https://btrfs.wiki.kernel.org/index.php/FAQ#How_much_free_space_do_I_have.3F
  
== Convert Ext3/4 to Btrfs ==
+
{{unsigned|03:28, 17 November 2016‎|Mearon}}
  
Just wondering about step #3: "Setup the network"
+
== Proposal to add lzo compression warning ==
I can't see any reason that this is needed. [[User:Capturts|Capturts]] ([[User talk:Capturts|talk]]) 18:35, 23 November 2012 (UTC)
+
The [https://wiki.debian.org/Btrfs Debian btrfs page] has a warning about compress=lzo being possibly dangerous, citing the [https://www.spinics.net/lists/linux-btrfs/msg56563.html thread here]. I propose adding a warning section that simply notes this possibility and cites either the Debian wiki, the linked thread, or both. -- [[User:altercation|altercation]]
  
: It's because of Step #5: Installing btrfs-progs. This is based off of the old install mediums, which  had local versions of programs, unless the remote repositories were enabled like in step #2. Since the new install mediums are remote-only (however they might have some filesystem tools on them), the entire section needs updating. [[User:Klink-a-dink-dink|Klink-a-dink-dink]] ([[User talk:Klink-a-dink-dink|talk]]) 01:06, 24 November 2012 (UTC)
+
:It might be worth a note pointing to the thread, ''but'' the user in that thread [https://www.spinics.net/lists/linux-btrfs/msg58676.html reports he was using RAID6], which is already warned against in the wiki article. The rest of it seems to be just guessing that lzo is affecting it. Hard to know since he was using RAID6.  -- [[User:Rdeckard|Rdeckard]] ([[User_talk:Rdeckard|talk]]) 00:50, 23 March 2017 (UTC)
 +
 
 +
== cp --reflink and the actual meaning of CoW ==
 +
 
 +
If one wishes to create a lightweight copy, --reflink must be used even on files with CoW enabled. Anyone on btrfs filesystem can easily test this. Claims of this being required for only files with CoW explicitly disabled are false. --reflink is not the same thing as CoW - this is better explained in https://btrfs.wiki.kernel.org/index.php/SysadminGuide#Copy_on_Write_.28CoW.29
 +
 
 +
Also https://unix.stackexchange.com/questions/80351/why-is-cp-reflink-auto-not-the-default-behaviour
 +
 
 +
{{unsigned|12:07, 27 May 2017‎|Vtj}}
 +
 
 +
: Right, thanks for fixing this in the article. -- [[User:Edh|Edh]] ([[User talk:Edh|talk]]) 11:43, 28 May 2017 (UTC)

Latest revision as of 11:44, 28 May 2017

Note: The name of the file system does not seem to have an official capitalization, so the rule for the ArchWiki has been arbitrarily set to use "Btrfs" (capital "B" and the rest lower-case); "btrfs" and "BTRFS" are therefore wrong spellings in this wiki. -- Kynikos (talk) 09:36, 6 January 2014 (UTC)

"Displaying used/free space" needs rewrite

Section "Displaying used/free space" needs a rewrite. I will hopefully do that when I have time.

—This unsigned comment is by Mearon (talk) 03:28, 17 November 2016‎. Please sign your posts with ~~~~!

Proposal to add lzo compression warning

The Debian btrfs page has a warning about compress=lzo being possibly dangerous, citing the thread here. I propose adding a warning section that simply notes this possibility and cites either the Debian wiki, the linked thread, or both. -- altercation

It might be worth a note pointing to the thread, but the user in that thread reports he was using RAID6, which is already warned against in the wiki article. The rest of it seems to be just guessing that lzo is affecting it. Hard to know since he was using RAID6. -- Rdeckard (talk) 00:50, 23 March 2017 (UTC)

cp --reflink and the actual meaning of CoW

If one wishes to create a lightweight copy, --reflink must be used even on files with CoW enabled. Anyone on btrfs filesystem can easily test this. Claims of this being required for only files with CoW explicitly disabled are false. --reflink is not the same thing as CoW - this is better explained in https://btrfs.wiki.kernel.org/index.php/SysadminGuide#Copy_on_Write_.28CoW.29

Also https://unix.stackexchange.com/questions/80351/why-is-cp-reflink-auto-not-the-default-behaviour

—This unsigned comment is by Vtj (talk) 12:07, 27 May 2017‎. Please sign your posts with ~~~~!

Right, thanks for fixing this in the article. -- Edh (talk) 11:43, 28 May 2017 (UTC)