On Thursday April 20, [EMAIL PROTECTED] wrote:
> (Please Cc me on any replies, I'm not on the list.)
Always!
> [ 37.406668] md: raid6 personality registered for level 6
> [ 37.726168] md: bind<dm-0>
> [ 37.729096] md: bind<dm-1>
> [ 37.742155] md: bind<dm-2>
> [ 37.745266] md: bind<dm-3>
> [ 47.736121] BUG: soft lockup detected on CPU#1!
> [ 47.740655]
> [ 47.740655] Call Trace: <IRQ> <ffffffff80247e68>{softlockup_tick+218}
> [ 47.748483] <ffffffff8022f59f>{update_process_times+66}
> <ffffffff80212ffa>{smp_local_timer_interrupt+35}
> [ 47.758681] <ffffffff80213614>{smp_apic_timer_interrupt+65}
> <ffffffff8020a106>{apic_timer_interrupt+98} <EOI>
> [ 47.769352] <ffffffff8028ad41>{mpage_writepages+730}
> <ffffffff802495bd>{find_get_pages+91}
> [ 47.778304] <ffffffff8024fd99>{pagevec_lookup+23}
> <ffffffff8025096d>{invalidate_mapping_pages+183}
> [ 47.787981] <ffffffff80212c8d>{smp_call_function+48}
> <ffffffff880c44e3>{:md_mod:do_md_run+664}
....
> [ 123.802707] raid5: device dm-3 operational as raid disk 3
> [ 123.808102] raid5: device dm-2 operational as raid disk 2
Wow! 76 second to set up a raid5 array - all of that invalidating an
inode which would not have had any valid data in it!
Can you try this patch please?
Thanks,
NeilBrown
-------------------
Signed-off-by: Neil Brown <[EMAIL PROTECTED]>
### Diffstat output
./fs/block_dev.c | 1 +
1 file changed, 1 insertion(+)
diff ./fs/block_dev.c~current~ ./fs/block_dev.c
--- ./fs/block_dev.c~current~ 2006-04-20 14:04:12.000000000 +1000
+++ ./fs/block_dev.c 2006-04-20 14:04:39.000000000 +1000
@@ -244,6 +244,7 @@ static struct inode *bdev_alloc_inode(st
struct bdev_inode *ei = kmem_cache_alloc(bdev_cachep, SLAB_KERNEL);
if (!ei)
return NULL;
+ inode_init_once(&ei->vfs_inode);
return &ei->vfs_inode;
}
-
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
