On Wed, Jul 15, 2009 at 1:16 PM, Chris Mason wrote:
> On Wed, Jul 15, 2009 at 12:23:47PM -0700, Dan Williams wrote:
>> On Mon, Jul 13, 2009 at 7:11 AM, David Woodhouse wrote:
>> > We'll want to use these in btrfs too.
>> >
>> > Signed-off-by: David Woodhouse
>>
>> Do you suspect that btrfs will al
On Wed, Jul 15, 2009 at 12:23:47PM -0700, Dan Williams wrote:
> On Mon, Jul 13, 2009 at 7:11 AM, David Woodhouse wrote:
> > We'll want to use these in btrfs too.
> >
> > Signed-off-by: David Woodhouse
>
> Do you suspect that btrfs will also want to perform these operations
> asynchronously? I am
On Mon, Jul 13, 2009 at 7:11 AM, David Woodhouse wrote:
> We'll want to use these in btrfs too.
>
> Signed-off-by: David Woodhouse
Do you suspect that btrfs will also want to perform these operations
asynchronously? I am preparing an updated release of the raid6
offload patch kit, but the previo
Hello,
Started running valgrind against btrfsck since e2fsck seemed to have a myriad of
problems. btrfsck was actually not in too bad shape, only like 5 or 6 normal
errors and maybe 5 leaks. The big leak is the "seen" extent cache that we don't
seem to do anything with. Since I'm not sure what
change 'goto done' to 'break' for the case of all device extents have
been freed, so that the code updates space information will be execute.
Signed-off-by: Yan Zheng
---
diff -urp 1/fs/btrfs/volumes.c 2/fs/btrfs/volumes.c
--- 1/fs/btrfs/volumes.c2009-06-12 21:32:39.847088561 +0800
+++ 2
use __le64 instead of u64 in on-disk structure definition.
Signed-off-by: Yan Zheng
---
diff -urp 1/fs/btrfs/ctree.h 2/fs/btrfs/ctree.h
--- 1/fs/btrfs/ctree.h 2009-07-03 08:08:34.148847040 +0800
+++ 2/fs/btrfs/ctree.h 2009-07-15 14:59:31.779493061 +0800
@@ -483,7 +483,7 @@ struct btrfs_shared_
