[PATCH] btrfs/async-thread: introduce macro BTRFS_WORKERS_IDLE_THRESH to replace the magic number 32 used for btrfs_workers->idle_thresh

2012-03-18 Thread Wang Sheng-Hui
Signed-off-by: Wang Sheng-Hui --- fs/btrfs/async-thread.c |2 +- fs/btrfs/async-thread.h |8 +++- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/fs/btrfs/async-thread.c b/fs/btrfs/async-thread.c index 5a7d756..2491096 100644 --- a/fs/btrfs/async-thread.c +++ b/fs/btrf

Re: getdents - ext4 vs btrfs performance

2012-03-18 Thread Ted Ts'o
On Thu, Mar 15, 2012 at 11:42:24AM +0100, Jacek Luczak wrote: > > That was not a SVN server. It was a build host having checkouts of SVN > projects. > > The many files/dirs case is common for VCS and the SVN is not the only > that would be affected here. Well, with SVN it's 2x or 3x the number

Re: Can't mount, power failure - recoverable?

2012-03-18 Thread Skylar Burtenshaw
> Looks like some of the bottom of this trace is missing.> That's because I'm amazing, Chris. I don't even know how that happened.. Trying again: BUG: unable to handle kernel NULL pointer dereference at 000$ IP: [] btrfs_put_block_group+0x11/0x70 [btrfs] PGD 78e80067 PUD 79588067 PMD 0 O

Re: Can't mount, power failure - recoverable?

2012-03-18 Thread Chris Mason
On Sat, Mar 17, 2012 at 07:06:14PM +, Skylar Burtenshaw wrote: > > The stack trace would be a start :p > > > Here's the trace. Mount attempt using 3.2.0; Looks like some of the bottom of this trace is missing. Can you please try to grab the whole thing? -chris > > [ 39.873019] device lab

Re: "scrub" stops the machine

2012-03-18 Thread Chris Samuel
On Sunday 18 March 2012 19:04:00 Helmut Hullen wrote: > Second try with kernel 3.2.5: same problem. My understanding is that all 3.2.x versions will have the same btrfs code, if you want to try with a newer version you'll need to try the 3.3 release candidates. cheers! Chris -- Chris Samuel

Re: "scrub" stops the machine

2012-03-18 Thread Helmut Hullen
Hallo, Martin, Du meintest am 17.03.12: btrfs scrub start /mnt/btr and all was dead. Really dead. No access via keybord, no access via SSH. >>> what kernel are you using? >> As mentioned some hours ago: 3.2.9 (self made). >>> Are you by any chance on a 32 bit masch