User: Password:
|
|
Subscribe / Log in / New account

The Btrfs filesystem: An introduction

The Btrfs filesystem: An introduction

Posted Dec 12, 2013 9:23 UTC (Thu) by ebirdie (guest, #512)
Parent article: The Btrfs filesystem: An introduction

Incidentally I just picked this up, FWIW adding to the list of real world usage, Netgear has put Btrfs into real world use in its ReadyNAS 312 appliance.

<http://www.anandtech.com/show/7500/netgear-readynas-312-2...>

I'm pretty confident there are other vendors too, but to me this was a wake-up for Btrfs.

Great that the editor is publishing the set of articles. Reading the article raised an interest to further information, what vendors/employers might have been active and how they have changed during the presented time period in development of Btrfs.


(Log in to post comments)

The Btrfs filesystem: An introduction

Posted Dec 18, 2013 23:18 UTC (Wed) by Lennie (guest, #49641) [Link]

My guess would be they use a large BTRFS filesystem on top of RAID and don't use the multi device support in BTRFS. This is one of the things Suse has also suggested, BTRFS is stable, without using multi device support.

The Btrfs filesystem: An introduction

Posted Dec 19, 2013 23:41 UTC (Thu) by Pc5Y9sbv (guest, #41328) [Link]

We've been testing BTRFS in this configuration (BTRFS formatted on one large hardware RAID disk) with mixed results.

We are formatting about 20-60 TB of raw disk space (different test scenarios), and copying a wide range of different data trees which include large files and huge numbers of small files generated by programs. There might be about 40-70 TB of uncompressed data in around 10M files (using compress-force=zlib, it shrinks to 10-15 TB).

We wanted to store near-line backups with daily/weekly/monthly snapshot history and it failed miserably. It seems we can use the transparent compression and good old-fashioned rsync --link-dest tricks to store our backup history, but if we instead try to take sub-volume snapshots and just keep modifying the "head" via rsync, it blows up and takes the filesystem with it. So, it can handle the huge number of inodes involved in representing trees millions of files for each day, but it cannot handle the equivalent sub-volume snapshot workload.

The Btrfs filesystem: An introduction

Posted Dec 19, 2013 23:46 UTC (Thu) by Lennie (guest, #49641) [Link]

Well, that is good news.

It's a start. Slowly but surely it also be (more) stable for other workloads.


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds