linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Btrfs features/stabilisation timeline?
       [not found] <21598622.8.1270576917138.JavaMail.root@zimbra>
@ 2010-04-06 18:09 ` Roy Sigurd Karlsbakk
  0 siblings, 0 replies; only message in thread
From: Roy Sigurd Karlsbakk @ 2010-04-06 18:09 UTC (permalink / raw)
  To: linux-btrfs

Hi all

With Sun^WOracle's changes to the Solaris license and more, Btrfs looks more welcome every day. However, I can't find anything about its progress for stabilisation or features, so I guess it miht be appropriate to ask here?

* How far is Btrfs to become "stable" as in for production use?
* I think I read a year back that RAID[56] support was started (merge of md code IIRC). How far has this come? Will it allow for what ZFS RAIDZ[123] can do?
* In ZFS, block sizes vary depending on file size on the same filesystem. Is this a feature that is wanted or that will (or is) included in Btrfs?
* In ZFS, some dedup has been added. I read somewhere this is a planned feature in Btrfs, but again, is it far away?
* ZFS is self-healing for device failures or sector errors, given sufficient redundancy with mirrors or raidz[123]. I guess this will the same in Btrfs?
* in ZFS, scrubbing takes up a very high amount of I/O, significantly reducing disk performance for the zpool (at least this is the case for 2009.06 and Solaris 10). Will there be done efforts to help avoding this with Btrfs?

Best regards

roy
--
Roy Sigurd Karlsbakk
(+47) 97542685
roy@karlsbakk.net
http://blogg.karlsbakk.net/

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2010-04-06 18:09 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <21598622.8.1270576917138.JavaMail.root@zimbra>
2010-04-06 18:09 ` Btrfs features/stabilisation timeline? Roy Sigurd Karlsbakk

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).