On 20.06.2018 10:34, Gandalf Corvotempesta wrote: > Il giorno mer 20 giu 2018 alle ore 02:06 waxhead > <waxhead@xxxxxxxxxxxxxx> ha scritto: >> First of all: I am not a BTRFS developer, but I follow the mailing list >> closely and I too have a particular interest in the "RAID"5/6 feature >> which realistically is probably about 3-4 years (if not more) in the future. > > Ok. > > [cut] > >> Now keep in mind that this is just a humble users analysis of the >> situation based on whatever I have picked up from the mailing list which >> may or may not be entirely accurate so take it for what it is! > > I wasn't aware of all of these "restrictions". > If this is true, now I understand why redhat lost interest in BTRFS. > 3-4 years more for a "working" RAID56 is absolutely too much, in this case, > ZFS support for RAID-Z expansion/reduction (actively being worked on) > will be released > much earlier (probably, a test working-version later this year and a > stable version next year) > > RAID-Z single disk espansion/removal is probably the real missing feature in ZFS > allowing it to be considered a general-purpose FS. > > Device removal was added some months ago and now is possible (so, if > you add a single disk to a mirrored vdev, > you don't have to destroy the whole pool to remove the accidentally-added disk) > > In 3-4 years, maybe oracle release ZFS as GPL-compatible (solaris is > dying, latest release is 3 years ago, > so there is no need to keep a FS opensource compatible only with a died OS) > > Keep in mind that i'm not a ZFS-fan (honestly, I don't like it) but > with these 2 features added and tons of restriction in BTRFS, > there is no other choise. Of course btrfs is open source and new contributors are always welcome. > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
