[PATCH] md: Avoid a deadlock when removing a device from an md array via sysfs.

2007-04-02 Thread NeilBrown
(This patch should go in 2.6.21 as it fixes a recent regression - NB) A device can be removed from an md array via e.g. echo remove /sys/block/md3/md/dev-sde/state This will try to remove the 'dev-sde' subtree which will deadlock since commit e7b0d26a86943370c04d6833c6edba2a72a6e240 With

Re: [PATCH] md: Avoid a deadlock when removing a device from an md array via sysfs.

2007-04-02 Thread Andrew Morton
On Mon, 2 Apr 2007 17:44:17 +1000 NeilBrown [EMAIL PROTECTED] wrote: (This patch should go in 2.6.21 as it fixes a recent regression - NB) A device can be removed from an md array via e.g. echo remove /sys/block/md3/md/dev-sde/state This will try to remove the 'dev-sde' subtree which

Re: [PATCH] md: Avoid a deadlock when removing a device from an md array via sysfs.

2007-04-02 Thread Neil Brown
On Monday April 2, [EMAIL PROTECTED] wrote: What guarantees that *rdev is still valid when delayed_delete() runs? Because that is how kobjects and krefs work. There is an embedded refcount etc etc.. And what guarantees that the md module hasn't been rmmodded when delayed_delete() tries

Re: raid5 write performance

2007-04-02 Thread Raz Ben-Jehuda(caro)
On 4/2/07, Dan Williams [EMAIL PROTECTED] wrote: On 3/30/07, Raz Ben-Jehuda(caro) [EMAIL PROTECTED] wrote: Please see bellow. On 8/28/06, Neil Brown [EMAIL PROTECTED] wrote: On Sunday August 13, [EMAIL PROTECTED] wrote: well ... me again Following your advice I added a

mismatch_cnt worries

2007-04-02 Thread Gavin McCullagh
Hi, I've relatively recently started using md having had some bad experiences with hardware raid controllers. I've had some really good experiences (stepwise upgrading a 800GB raid5 array to 1.5TB one by exchanging disks and using mdadm --grow), but am in the middle of a more worrying one. I

Question about using dmraid45 patch

2007-04-02 Thread Wood, Brian J
Hello, I'm new to the dm-devel mail list, so hopefully my question won't get flamed too badly :) I need some help with a setup issue in dmraid, specifically raid5. I'm trying to use Heinz Mauelshagen's patch for dmraid45 and having problems getting it to compile in the kernel (or as a module).

Re: mismatch_cnt worries

2007-04-02 Thread Neil Brown
On Monday April 2, [EMAIL PROTECTED] wrote: Neil's post here suggests either this is all normal or I'm seriously up the creek. http://www.mail-archive.com/linux-raid@vger.kernel.org/msg07349.html My questions: 1. Should I be worried or is this normal? If so can you explain why

bio too big device md1 (16 8)

2007-04-02 Thread syrius . ml
Hi, i'm using 2.6.21-rc5-git9 + http://www.kernel.org/pub/linux/kernel/people/agk/patches/2.6/editing/dm-merge-max_hw_sector.patch ( i've been testing with and without it, and first encountered it on 2.6.18-debian ) I've setup a raid1 array md1 (it was created in a degraded mode using the

Re: 2.6.20.3 AMD64 oops in CFQ code

2007-04-02 Thread Tejun Heo
[resending. my mail service was down for more than a week and this message didn't get delivered.] [EMAIL PROTECTED] wrote: Anyway, what's annoying is that I can't figure out how to bring the drive back on line without resetting the box. It's in a hot-swap enclosure, but power cycling the