Hello,
Now i trying the patch....
[EMAIL PROTECTED] root]# mdadm -G --bitmap=/raid.bm /dev/md0
mdadm: Warning - bitmaps created on this kernel are not portable
between different architectured. Consider upgrading the Linux kernel.
mdadm: Cannot set bitmap file for /dev/md0: Cannot allocate memory
[EMAIL PROTECTED] root]# free
total used free shared buffers cached
Mem: 2073152 75036 1998116 0 4 29304
-/+ buffers/cache: 45728 2027424
Swap: 0 0 0
[EMAIL PROTECTED] root]# mdadm -X /dev/md0
mdadm: WARNING: bitmap file is not large enough for array size
2641363663419644516!
Filename : /dev/md0
Magic : a799d766
mdadm: invalid bitmap magic 0xa799d766, the bitmap file appears to be
corrupted
Version : -91455910
mdadm: unknown bitmap version -91455910, either the bitmap file is corrupted
or you need to upgrade your tools
[EMAIL PROTECTED] root]#
And now what? :-)
Cheers,
Janos
----- Original Message -----
From: "Neil Brown" <[EMAIL PROTECTED]>
To: "JaniD++" <[EMAIL PROTECTED]>
Cc: <[email protected]>
Sent: Friday, December 09, 2005 5:49 AM
Subject: Re: RAID5 resync question BUGREPORT!
> On Friday December 9, [EMAIL PROTECTED] wrote:
> > Hi,
> >
> > After i get this on one of my disk node, imediately send this letter,
and go
> > to the hosting company, to see, is any message on the screen.
> > But unfortunately nothing what i found.
> > simple freeze.
> > no message, no ping, no num lock!
> >
> > The full message of the node next reboot is here:
> > http://download.netcenter.hu/bughunt/20051209/boot.log
>
> Ahh.... Ok, I know the problem.
> I had originally only tested bitmaps for raid5 and raid6 on a
> single-processor machine. When you try it on an SMP machine you get a
> deadlock.
> The following patch - which will be in 2.6.15 - fixes the problem.
>
> Thanks for your testing.
>
> NeilBrown
>
> -------------------------------
> Fix locking problem in r5/r6
>
> bitmap_unplug actually writes data (bits) to storage, so we
> shouldn't be holding a spinlock...
>
> Signed-off-by: Neil Brown <[EMAIL PROTECTED]>
>
> ### Diffstat output
> ./drivers/md/raid5.c | 2 ++
> ./drivers/md/raid6main.c | 2 ++
> 2 files changed, 4 insertions(+)
>
> diff ./drivers/md/raid5.c~current~ ./drivers/md/raid5.c
> --- ./drivers/md/raid5.c 2005-12-06 11:06:53.000000000 +1100
> +++ ./drivers/md/raid5.c~current~ 2005-12-06 11:07:10.000000000 +1100
> @@ -1704,7 +1704,9 @@ static void raid5d (mddev_t *mddev)
>
> if (conf->seq_flush - conf->seq_write > 0) {
> int seq = conf->seq_flush;
> + spin_unlock_irq(&conf->device_lock);
> bitmap_unplug(mddev->bitmap);
> + spin_lock_irq(&conf->device_lock);
> conf->seq_write = seq;
> activate_bit_delay(conf);
> }
>
> diff ./drivers/md/raid6main.c~current~ ./drivers/md/raid6main.c
> --- ./drivers/md/raid6main.c 2005-12-06 11:06:53.000000000 +1100
> +++ ./drivers/md/raid6main.c~current~ 2005-12-06 11:07:10.000000000 +1100
> @@ -1784,7 +1784,9 @@ static void raid6d (mddev_t *mddev)
>
> if (conf->seq_flush - conf->seq_write > 0) {
> int seq = conf->seq_flush;
> + spin_unlock_irq(&conf->device_lock);
> bitmap_unplug(mddev->bitmap);
> + spin_lock_irq(&conf->device_lock);
> conf->seq_write = seq;
> activate_bit_delay(conf);
> }
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
