Difference between revisions of "Talk:Btrfs"

From ArchWiki
Jump to: navigation, search
(RAID-1 or RAID-5?: see btrfs wiki)
(Things to do: new section)
Line 21: Line 21:
  
 
the genfstab script puts a '1' in for 'pass' by default
 
the genfstab script puts a '1' in for 'pass' by default
 +
 +
== Things to do ==
 +
 +
Here are some items that seem to need addressing on this article. I am working on various parts of it at the moment.
 +
# Section relating to mounting and options.
 +
# Clean-up "Creating a new filesytem" section.
 +
# Create "Tips and tricks" section.
 +
## Add skinny extents.
 +
# Clean-up and clarify "Sub-volumes section"
 +
# Add section on Quotas
 +
# Reflow headings.
 +
## Break-up the flow more. Give readers more pauses.
 +
 +
[[User:AdamT|AdamT]] ([[User_talk:AdamT|Talk]]) 08:27, 28 November 2013 (UTC)

Revision as of 08:27, 28 November 2013

Comment about stability

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. Vikingurinn (talk) 16:52, 17 December 2012 (UTC)

RAID-1 or RAID-5?

"3 1TB disks in an md based raid1 yields a /dev/md0 with 1TB free space and the ability to safely loose 2 disks without losing data. 3 1TB disks in a btrfs volume with data=raid1 will allow the storage of approximately 1.5TB of data before reporting full. Only 1 disk can safely be lost without losing data."

That sounds more like some kind of weird, inefficient RAID-5 arrangement than RAID-1. I don't know btrfs enough to say it's wrong, but I know RAID-1 enough to question it?

Fukawi2 (talk) 23:52, 29 April 2013 (UTC)

See btrfs wiki:
btrfs combines all the drives into a storage pool first, and then duplicates the chunks as file data is created. RAID-1 is defined currently as "2 copies of all the data on different disks". This differs from MD-RAID and dmraid, in that those make exactly n copies for n disks. In a btrfs RAID-1 on 3 1TB drives we get 1.5TB of usable data. Because each block is only copied to 2 drives, writing a given block only requires exactly 2 drives spin up, reading requires only 1 drive to spinup.
-- Karol (talk) 15:59, 17 June 2013 (UTC)

btrfs with fsck hook and fstab pass

Apparently one does not need to have a btrfs partition fscked on boot, so there should be a '0' for 'pass' in the fstab for any btrfs partion. I had relatively slow boot ups with a pass of '1' (btrfs was root)

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/791020/comments/27

the genfstab script puts a '1' in for 'pass' by default

Things to do

Here are some items that seem to need addressing on this article. I am working on various parts of it at the moment.

  1. Section relating to mounting and options.
  2. Clean-up "Creating a new filesytem" section.
  3. Create "Tips and tricks" section.
    1. Add skinny extents.
  4. Clean-up and clarify "Sub-volumes section"
  5. Add section on Quotas
  6. Reflow headings.
    1. Break-up the flow more. Give readers more pauses.

AdamT (Talk) 08:27, 28 November 2013 (UTC)