ap> 2) there are still bugs that *must* be fixed before Btrfs can ap> be seriously considered: ap> http://www.mail-archive.com/linux-bt...@vger.kernel.org/msg05130.htmlI really don't think that's a show-stopper. He filled the disk with 2KB files. HE FILLED THE DISK WITH 2KB FILES.
Well, if there was a 50% overhead, then fine. That can happen. 80%? All right, still good... But what actually happened does not seem acceptable to me.
It's more, ``you think you're so clever, but you're not, see?'' I'm not saying not to fix it. I'm saying it's not a show-stopper.
I'm not saying it's a showstopper. I just don't think anyone could seriously consider a production deployment before this is fixed. Edward Shishkin is the maintainer and co-author of Reiser4, which has not been accepted into the kernel yet, despite the fact that many people have been using it successfully for years. (I am also one of the Reiser4 users and run it on some laptops I maintain.) So Edward's reaction is not surprising. ;-) It's like „hey! My stable filesystem stays out, but various experiments (EXT4, NILFS2, Btrfs, ...) are let in! How comes?“ Andrej
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
