söndag 05 februari 2012 18:55:58 skrev Dag Nygren: > Hi! > > Using lessfs on top of an XFS on top on a software RAID-5 and see this > freeze happening about once a week. Usually during heavy load. No comments on the stuff below? Nobody else? Increased the stripe_cache_size to 4096 according to the workaround for ths old similiar bug. Is the bug back in the recent kernels? Has not seen any freezes since that workaround but oth they weren't that frequent earlier either. > Feb 5 02:51:04 mythserv kernel: INFO: task lessfs:2687 blocked for more than > 120 seconds. > Feb 5 02:51:04 mythserv kernel: “echo 0 > > /proc/sys/kernel/hung_task_timeout_secs” disables this message. > Feb 5 02:51:04 mythserv kernel: lessfs D ffff88006faf1998 0 2687 1 > 0×00000000 Feb 5 02:51:04 mythserv kernel: ffff880066579828 > 0000000000000086 ffff8800665797b8 ffffffff00000000 > Feb 5 02:51:04 mythserv kernel: ffff88006faf1620 0000000000013300 > ffff880066579fd8 ffff880066578010 > Feb 5 02:51:04 mythserv kernel: ffff880066579fd8 0000000000013300 > ffffffff81655020 ffff88006faf1620 > Feb 5 02:51:04 mythserv kernel: Call Trace: > Feb 5 02:51:04 mythserv kernel: [] schedule+0x3f/0×60 > Feb 5 02:51:04 mythserv kernel: [] get_active_stripe+0x2ea/0×790 [raid456] > Feb 5 02:51:04 mythserv kernel: [] ? try_to_wake_up+0x2b0/0x2b0 > Feb 5 02:51:04 mythserv kernel: [] make_request+0x1ae/0×460 [raid456] > Feb 5 02:51:04 mythserv kernel: [] ? wake_up_bit+0×40/0×40 > Feb 5 02:51:04 mythserv kernel: [] md_make_request+0xd5/0×200 > Feb 5 02:51:04 mythserv kernel: [] generic_make_request+0xbf/0xf0 > Feb 5 02:51:04 mythserv kernel: [] submit_bio+0×85/0×110 > Feb 5 02:51:04 mythserv kernel: [] ? __bio_add_page+0×110/0×250 > Feb 5 02:51:04 mythserv kernel: [] xfs_submit_ioend_bio+0×57/0×80 [xfs] > Feb 5 02:51:04 mythserv kernel: [] xfs_submit_ioend+0xf6/0×110 [xfs] > Feb 5 02:51:04 mythserv kernel: [] xfs_vm_writepage+0×230/0×500 [xfs] > Feb 5 02:51:04 mythserv kernel: [] __writepage+0×17/0×40 > Feb 5 02:51:04 mythserv kernel: [] write_cache_pages+0×221/0x4a0 > Feb 5 02:51:04 mythserv kernel: [] ? tomoyo_init_request_info+0x3f/0×70 > Feb 5 02:51:04 mythserv kernel: [] ? set_page_dirty+0×70/0×70 > Feb 5 02:51:04 mythserv kernel: [] generic_writepages+0×51/0×80 > Feb 5 02:51:04 mythserv kernel: [] xfs_vm_writepages+0×53/0×70 [xfs] > Feb 5 02:51:04 mythserv kernel: [] do_writepages+0×21/0×40 > Feb 5 02:51:04 mythserv kernel: [] __filemap_fdatawrite_range+0x5b/0×60 > Feb 5 02:51:04 mythserv kernel: [] filemap_write_and_wait_range+0x5a/0×80 > Feb 5 02:51:04 mythserv kernel: [] xfs_file_fsync+0×68/0x2d0 [xfs] > Feb 5 02:51:04 mythserv kernel: [] vfs_fsync_range+0x2b/0×40 > Feb 5 02:51:04 mythserv kernel: [] vfs_fsync+0x1c/0×20 > Feb 5 02:51:04 mythserv kernel: [] do_fsync+0x3a/0×60 > Feb 5 02:51:04 mythserv kernel: [] sys_fsync+0×10/0×20 > Feb 5 02:51:04 mythserv kernel: [] system_call_fastpath+0×16/0x1b > > Any hints? Or any debugging I can do to help? I did find a similar cas from > 2008, but that is supposed to be fixed now. > This also started after updating the kernel to the 3.x series. At the moment > using 3.2.2 and still seeing it. -- Dag Nygren email: dag@xxxxxxxxxx Oy Espoon NewTech Ab phone: +358 9 8024910 Träsktorpet 3 fax: +358 9 8024916 02360 ESBO Mobile: +358 400 426312 FINLAND -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
