Re: Release plan

2009-06-25 Thread Mike Ramsey
Valerie Aurora redhat.com> writes: [snip] > > :) Zettabyte, perhaps? Sigh. Yes, Zettabyte. I am going to have a talk with my subconscious about that. :-) > > -VAL > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majordomo vger.kern

Re: Release plan

2009-06-25 Thread Valerie Aurora
On Wed, Jun 24, 2009 at 01:11:24AM +, Mike Ramsey wrote: > Miguel F Mascarenhas Sousa Filipe gmail.com> writes: > > [snip] > > > > You mean ZFS, but I think everybody who read this "self-corrected" your > > typo. > > Yes, I mean ZFS. ZFS used to be known as the Zettapoint File System. >

[PATCH] btrfs: 'usertrans' mount option to allow unprivileged userspace transactions

2009-06-25 Thread Sage Weil
This lets an administrator give non-root users access to the btrfs transaction start/end ioctls via a mount option. Currently any process using the ioctls must run as root. That's appropriate in general, since the ioctls allow let any process to hang fs commits by holding an open transaction i

[PATCH] btrfs: make flushoncommit correctly wait on ordered_extents

2009-06-25 Thread Sage Weil
Hi Chris, The commit_transaction call to wait_ordered_extents when snap_pending passes nocow_only=1 to process only NOCOW or PREALLOC extents. This isn't correct for the 'flushoncommit' mode, as it skips extents we just started IO on in start_delalloc_inodes. So, in the flushoncommit case, wa

[PATCH] btrfs: async block group caching v5

2009-06-25 Thread Josef Bacik
This patch moves the caching of the block group off to a kthread in order to allow people to allocate sooner. Instead of blocking up behind the caching mutex, we instead kick of the caching kthread, and then attempt to make an allocation. If we cannot, we wait on the block groups caching waitqueu

[PATCH] btrfs: use hybrid extents+bitmap rb tree for free space cache: V4

2009-06-25 Thread Josef Bacik
Currently btrfs has a problem where it can use a ridiculous amount of RAM simply tracking free space. As free space gets fragmented, we end up with thousands of entries on an rb-tree per block group, which usually spans 1 gig of area. Since we currently don't ever flush free space cache back to d

Re: Phoronix article slaming BTRFS

2009-06-25 Thread Stephan von Krawczynski
On Wed, 24 Jun 2009 19:38:37 +0200 Jens Axboe wrote: > [...] > It's easy to throw cache at the problem and make it faster. That's like > shaving weight off a car. Might make it go faster, definitely wont make > it safer. Interestingly nobody talks about "the other end" of the ssd market. Ok, a c