News for hackers. Stuff that matters.
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by Thaxll on Friday August 05, 2016 @11:38AM (#12233125)
The thing that need 8/16GB of ram to run. Creating a solid FS takes time, ZFS is good because it has been around for 10years.
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by olavgg on Friday August 05, 2016 @11:49AM (#12233213)
ZFS runs fine with just 1GB of ram. Even several terrabytes of storage. When it comes to knowledge about ZFS, avoid about anything that comes from the FreeNAS community. It is quackery at its best.
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by gsnedders on Friday August 05, 2016 @12:37PM (#12233682)
The problem is that there's so much quackery around ZFS when you Google for answers to any major problem. It's frequently hard to get good information.
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by Terribledactyl on Friday August 05, 2016 @01:20PM (#12234112)
I just want to point out that the official documentation is absolutely great.

http://docs.oracle.com/cd/E19253-01/819-5461/

Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by the8472 on Friday August 05, 2016 @12:43PM (#12233738)
Doesn't ZFS dedup eat lots of ram? btrfs offers on-demand deduplication instead of it being always-on.
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by snuxoll on Friday August 05, 2016 @01:00PM (#12233934)
Yes, it does. But dedup is rarely that useful in my experience, it sounds nice on paper but it often doesn't provide benefits worth the CPU and IOPS demand it generates. Compression is "good enough" 98% of the time, and ZFS does a fine job with it.
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by unhammer on Friday August 05, 2016 @06:40PM (#12236178)
If you take snapshotted backups from ext4 etc filsystems (no send/recv), where users regularly reorganise photo folders, dedup is invaluable :-)
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by the8472 on Friday August 05, 2016 @01:18PM (#12234092)
dedup is quite useful when you have snapshots that somehow have lost their space-sharing. I guess it's due to files being replaced with identical files.
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by rleigh on Friday August 05, 2016 @03:19PM (#12235071)
The Btrfs deduplication... also needs vast quantities of RAM. That's just the nature of the beast. Don't use it, and both systems have relatively modest requirements.
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by the8472 on Friday August 05, 2016 @03:42PM (#12235225)
but it's on-demand and can use a scratch file, which makes it far more managable, e.g. you can let it run over the weekend.
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by pmarreck on Friday August 05, 2016 @01:11PM (#12234043)
If you need filesystem dedup... Perhaps handle it in userspace instead
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by the8472 on Friday August 05, 2016 @01:19PM (#12234100)
Since ZoL does not have reflink copies or the range-dedup ioctl you cannot do it from userspace like you can with btrfs.
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by oofabz on Friday August 05, 2016 @01:57PM (#12234438)
I run ZFS on a VM with 512MB RAM. It does web/mail/file serving and it has worked great.
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by cm3 on Friday August 05, 2016 @11:48AM (#12233205)
Isn't that just for the default dedup implementation where it's suggested to have 2-5GB per TB?

HAMMER fs can dedup with little RAM, but the ZFS devs aren't ignorant or uninformed, so I would expect them to have a plan to remedy the inefficiency of OpenZFS's dedup implementation. I know there are commercially avaialbe alternaitve dedup versions, but I don't have any experience with those.

Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by williamstein on Friday August 05, 2016 @11:46AM (#12233185)
Btrfs entered the Linux kernel over 7 years ago. (I've used both btrfs and ZFS a lot in production and would never touch btrfs again. I really like ZFS though.)
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by Thaxll on Friday August 05, 2016 @11:59AM (#12233320)
"The development of Btrfs began in 2007, and by August 2014, the file system's on-disk format has been marked as stable."
Re:Btrfs RAID 5/6 Code Found to Be Very Unsafe and Will Like... by rleigh on Friday August 05, 2016 @03:17PM (#12235053)
The on-disk format is the least of the problems with Btrfs. The quality of the implementation of the filesystem which uses that format is the bigger issue. It's still awful, and I've been using it since the start.

Two years ago, I migrated everything to ZFS and haven't looked back. It works. It hasn't lost any data, and it's easy to set up and administer. I can't give it any higher praise than that. It does its stuff with no fuss or drama.