Hello, Trying to put together a list of TODO items for btrfs so we can update the wiki page fully. So far these things are on the list * Proper ENOSPC handling * O_DIRECT support (without checksumming) * AIO support * Subvolume quotas and inherited space usage information * Snapshot removal * QA Suite for automated regression testing * Reserved space for online fsck and the ability to add storage so that a * background extent allocation check can proceed * Additional ioctls to set per-inode attributes (nodatacow, nodatasum, etc) So I think all of those are still true. Things that I know are being worked on are * async block group cacheing - me * locking changes - Chris * backref stuff - Yan Som other things off the top of my head are * a better way to cache block groups in general, for this I was thinking of a bitmap or something like that per block group of free space * space balancing. this will likely need to wait on proper ENOSPC handling * grub support :) Thats all that I can think of atm. Add things to the list if you think of them, and hopefully we can update the wiki early next week. Thanks, Josef -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Apr 09, 2009 at 12:24:18PM -0400, Josef Bacik wrote:> Hello, > > Trying to put together a list of TODO items for btrfs so we can update the wiki > page fully. So far these things are on the list > > * Proper ENOSPC handling > * O_DIRECT support (without checksumming) > * AIO support > * Subvolume quotas and inherited space usage information > * Snapshot removal > * QA Suite for automated regression testing > * Reserved space for online fsck and the ability to add storage so that a > * background extent allocation check can proceed > * Additional ioctls to set per-inode attributes (nodatacow, nodatasum, etc) > > So I think all of those are still true. Things that I know are being worked on > are > > * async block group cacheing - me > * locking changes - Chris > * backref stuff - Yan > > Som other things off the top of my head are > > * a better way to cache block groups in general, for this I was thinking of a > bitmap or something like that per block group of free space > * space balancing. this will likely need to wait on proper ENOSPC handling > * grub support :) > > Thats all that I can think of atm. Add things to the list if you think of them, > and hopefully we can update the wiki early next week. Thanks,Long-term (post 1.0 release I assume): * Block based deduplication (not file-based) :-) Ray -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Josef Bacik wrote:> Hello, > > Trying to put together a list of TODO items for btrfs so we can updatethe wiki> page fully. So far these things are on the list > > * Proper ENOSPC handling > * O_DIRECT support (without checksumming) > * AIO support > * Subvolume quotas and inherited space usage information > * Snapshot removal > * QA Suite for automated regression testing > * Reserved space for online fsck and the ability to add storage so that a > * background extent allocation check can proceed > * Additional ioctls to set per-inode attributes (nodatacow, nodatasum,etc)> > So I think all of those are still true. Things that I know are beingworked on> are > > * async block group cacheing - me > * locking changes - Chris > * backref stuff - Yan > > Som other things off the top of my head are > > * a better way to cache block groups in general, for this I wasthinking of a> bitmap or something like that per block group of free space > * space balancing. this will likely need to wait on proper ENOSPChandling> * grub support :)I''m doing some work in the area of more robust error handling. My patch set is a little stale now but I''m going to spend some time this week bringing it back to life. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEUEARECAAYFAknePtAACgkQLPWxlyuTD7LNmQCeOU4VxDmHIaI/lzgMHqCho7Vi uasAl1Iggk87F9YEj1g1KDir5boWsYI=H7Yx -----END PGP SIGNATURE----- -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Apr 09, 2009 at 02:30:40PM -0400, Jeff Mahoney wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Josef Bacik wrote: > > Hello, > > > > Trying to put together a list of TODO items for btrfs so we can update > the wiki > > page fully. So far these things are on the list > > > > * Proper ENOSPC handling > > * O_DIRECT support (without checksumming) > > * AIO support > > * Subvolume quotas and inherited space usage information > > * Snapshot removal > > * QA Suite for automated regression testing > > * Reserved space for online fsck and the ability to add storage so that a > > * background extent allocation check can proceed > > * Additional ioctls to set per-inode attributes (nodatacow, nodatasum, > etc) > > > > So I think all of those are still true. Things that I know are being > worked on > > are > > > > * async block group cacheing - me > > * locking changes - Chris > > * backref stuff - Yan > > > > Som other things off the top of my head are > > > > * a better way to cache block groups in general, for this I was > thinking of a > > bitmap or something like that per block group of free space > > * space balancing. this will likely need to wait on proper ENOSPC > handling > > * grub support :) > > I''m doing some work in the area of more robust error handling. My patch > set is a little stale now but I''m going to spend some time this week > bringing it back to life. >Ahh yeah thats a good thing. At some point I''d like to turn on all of the "inject faults" crap and make sure we handle ENOMEM and such properly and such. Thanks, Josef -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
I''m working on O_DIRECT support... but with checksumming. I''ve also been looking at AIO but directio is first. jim -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
At 05:23 09/04/10, jim owens wrote:>I''m working on O_DIRECT support... but with checksumming. > >I''ve also been looking at AIO but directio is first. >Hi I am interesting in and looking forward to your O_DIRECT code. When are you going to send prototype or alpha version patch? -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Josef, On Thu, 2009-04-09 at 12:24 -0400, Josef Bacik wrote:> Hello, > > Trying to put together a list of TODO items for btrfs so we can update the wiki > page fully. So far these things are on the list > > * Proper ENOSPC handling > * O_DIRECT support (without checksumming) > * AIO support > * Subvolume quotas and inherited space usage information > * Snapshot removal > * QA Suite for automated regression testingWe at LTP would be interested in the above. Please let us know your plans in doing Btrfs testing in any ways you do. Regards-- Subrata> * Reserved space for online fsck and the ability to add storage so that a > * background extent allocation check can proceed > * Additional ioctls to set per-inode attributes (nodatacow, nodatasum, etc) > > So I think all of those are still true. Things that I know are being worked on > are > > * async block group cacheing - me > * locking changes - Chris > * backref stuff - Yan > > Som other things off the top of my head are > > * a better way to cache block groups in general, for this I was thinking of a > bitmap or something like that per block group of free space > * space balancing. this will likely need to wait on proper ENOSPC handling > * grub support :) > > Thats all that I can think of atm. Add things to the list if you think of them, > and hopefully we can update the wiki early next week. Thanks, > > Josef > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majordomo@vger.kernel.org > 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Josef, On Fri, 2009-04-10 at 12:12 +0530, Subrata Modak wrote:> Hi Josef, > > On Thu, 2009-04-09 at 12:24 -0400, Josef Bacik wrote: > > Hello, > > > > Trying to put together a list of TODO items for btrfs so we can update the wiki > > page fully. So far these things are on the list > > > > * Proper ENOSPC handling > > * O_DIRECT support (without checksumming) > > * AIO support > > * Subvolume quotas and inherited space usage information > > * Snapshot removal > > * QA Suite for automated regression testing > > We at LTP would be interested in the above. Please let us know your > plans in doing Btrfs testing in any ways you do. >Any thoughts for us ? Regards-- Subrata> Regards-- > Subrata > > > * Reserved space for online fsck and the ability to add storage so that a > > * background extent allocation check can proceed > > * Additional ioctls to set per-inode attributes (nodatacow, nodatasum, etc) > > > > So I think all of those are still true. Things that I know are being worked on > > are > > > > * async block group cacheing - me > > * locking changes - Chris > > * backref stuff - Yan > > > > Som other things off the top of my head are > > > > * a better way to cache block groups in general, for this I was thinking of a > > bitmap or something like that per block group of free space > > * space balancing. this will likely need to wait on proper ENOSPC handling > > * grub support :) > > > > Thats all that I can think of atm. Add things to the list if you think of them, > > and hopefully we can update the wiki early next week. Thanks, > > > > Josef > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > > the body of a message to majordomo@vger.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > High Quality Requirements in a Collaborative Environment. > Download a free trial of Rational Requirements Composer Now! > http://p.sf.net/sfu/www-ibm-com > _______________________________________________ > Ltp-list mailing list > Ltp-list@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ltp-list-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html