Skip to contentSkip to conversation

Btrfs TODO

DISCUSSION Josef Bacik 6 participants 8 messages Apr 9, 2009 – Apr 13, 2009 Btrfs file system

lore
Share & tools
lore
#0 lore raw

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

#1 lore raw
Quoted 24 lines · Josef Bacik

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

Quoted 7 lines

* 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

#2 lore raw
In reply to Josef Bacik

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 3 lines · Josef Bacik

Hello,

Trying to put together a list of TODO items for btrfs so we can update

the wiki

Quoted 11 lines

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)

Quoted 2 lines

So I think all of those are still true. Things that I know are being

worked on

Quoted 9 lines

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

Quoted 2 lines

bitmap or something like that per block group of free space
* space balancing. this will likely need to wait on proper ENOSPC

handling

Quoted 1 line

* 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-----

#3 lore raw
Quoted 33 lines · Jeff Mahoney

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 3 lines · Josef Bacik

Hello,

Trying to put together a list of TODO items for btrfs so we can update

the wiki

Quoted 11 lines

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)

Quoted 2 lines

So I think all of those are still true. Things that I know are being

worked on

Quoted 9 lines

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

Quoted 9 lines
Quoted 2 lines

bitmap or something like that per block group of free space
* space balancing. this will likely need to wait on proper ENOSPC

handling

Quoted 1 line

* 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

#4 lore raw

I'm working on O_DIRECT support... but with checksumming.

I've also been looking at AIO but directio is first.

jim

#5 lore raw
Quoted 4 lines · jim owens

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?

#6 lore raw
In reply to Josef Bacik

Hi Josef,

Quoted 11 lines · Josef Bacik

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.

Regards--
Subrata

Quoted 26 lines

* 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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#7 lore raw

Hi Josef,

Quoted 15 lines · Subrata Modak

Hi Josef,

Quoted 11 lines · Josef Bacik

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

Quoted 3 lines

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

Quoted 40 lines

Regards--
Subrata

Quoted 18 lines

* 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 :)

Quoted 8 lines

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 [email protected]
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 [email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list