Re: [RFC PATCH v2 0/3] Btrfs: apply the Probabilistic Skiplist on btrfs

2012-01-13 Thread Andi Kleen
For the btrfs extent cache it's unclear if just RCUing is a good fit anyways: some workloads are very write heavy and RCU only performs well if you have a lot more reads than writes. For write heavy RCUification usually slows it down. FWIW, I'm mentioning this out of self interest - I need a

Re: Bug(?): btrfs carries on working if part of a device disappears

2012-01-13 Thread Liu Bo
On 01/06/2012 02:02 AM, Maik Zumstrull wrote: Hello list, I hit a funny BIOS bug the other day where the BIOS suddenly sets a HPA on a random hard disk, leaving only the first 33 MB accessible. That disk had one device of a multi-device btrfs on it in my case. (With dm-crypt/LUKS in

Re: Bug(?): btrfs carries on working if part of a device disappears

2012-01-13 Thread Ben Klein
On 13 January 2012 23:07, Liu Bo liubo2...@cn.fujitsu.com wrote: On 01/06/2012 02:02 AM, Maik Zumstrull wrote: Hello list, I hit a funny BIOS bug the other day where the BIOS suddenly sets a HPA on a random hard disk, leaving only the first 33 MB accessible. That disk had one device of a

[PATCH] Btrfs: add a delalloc mutex to inodes for delalloc reservations

2012-01-13 Thread Josef Bacik
I was using i_mutex for this, but we're getting bogus lockdep warnings by doing that and theres no real way to get rid of those, so just stop using i_mutex to protect delalloc metadata reservations and use a delalloc mutex instead. This shouldn't be contended often at all, only if you are writing

[PATCH] Btrfs: space leak tracepoints

2012-01-13 Thread Josef Bacik
This in addition to a script in my btrfs-tracing tree will help track down space leaks when we're getting space left over in block groups on umount. Thanks, Signed-off-by: Josef Bacik jo...@redhat.com --- fs/btrfs/delayed-inode.c | 45

Can't resize second device in RAID1

2012-01-13 Thread Marco L. Crociani
Hi, the situation: Label: 'RootFS'  uuid: c87975a0-a575-405e-9890-d3f7f25bbd96     Total devices 2 FS bytes used 284.98GB     devid    2 size 311.82GB used 286.51GB path /dev/sdb3     devid    1 size 897.76GB used 286.51GB path /dev/sda3 RootFS created when sda3 was 897.76GB and sdb3 311.82GB. I

Re: Can't resize second device in RAID1

2012-01-13 Thread Hugo Mills
On Sat, Jan 14, 2012 at 12:12:06AM +0100, Marco L. Crociani wrote: Hi, the situation: Label: 'RootFS'  uuid: c87975a0-a575-405e-9890-d3f7f25bbd96     Total devices 2 FS bytes used 284.98GB     devid    2 size 311.82GB used 286.51GB path /dev/sdb3     devid    1 size 897.76GB used 286.51GB

Re: Can't resize second device in RAID1

2012-01-13 Thread Marco L. Crociani
On Sat, Jan 14, 2012 at 12:17 AM, Hugo Mills h...@carfax.org.uk wrote: On Sat, Jan 14, 2012 at 12:12:06AM +0100, Marco L. Crociani wrote: Hi, the situation: Label: 'RootFS'  uuid: c87975a0-a575-405e-9890-d3f7f25bbd96     Total devices 2 FS bytes used 284.98GB     devid    2 size 311.82GB