Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757769Ab3FLTnw (ORCPT ); Wed, 12 Jun 2013 15:43:52 -0400 Received: from mx1.redhat.com ([209.132.183.28]:3111 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756370Ab3FLTnv (ORCPT ); Wed, 12 Jun 2013 15:43:51 -0400 Date: Wed, 12 Jun 2013 15:43:46 -0400 From: Dave Jones To: Linux Kernel Cc: linux-scsi@vger.kernel.org Subject: WARNING: at drivers/scsi/scsi_lib.c:1196 scsi_setup_fs_cmnd during RAID5 startup. Message-ID: <20130612194346.GD15200@redhat.com> Mail-Followup-To: Dave Jones , Linux Kernel , linux-scsi@vger.kernel.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3195 Lines: 63 3.10 seems to have a problem with dirty RAID5 sets. I've got a machine that panics on boot during RAID5 activation. After switching the BUG_ON to a WARN_ON, I was able to get this over serial console.. md/raid:md0: not clean -- starting background reconstruction md/raid:md0: device sdd1 operational as raid disk 2 md/raid:md0: device sdc1 operational as raid disk 1 md/raid:md0: device sdb1 operational as raid disk 0 md/raid:md0: allocated 3300kB md/raid:md0: raid level 5 active with 3 out of 3 devices, algorithm 2 md0: detected capacity change from 0 to 499847790592 md: resync of RAID array md0 md: minimum _guaranteed_ speed: 1000 KB/sec/disk. md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for resync. md: using 128k window, over a total of 244066304k. md: resuming resync of md0 from checkpoint. WARNING: at drivers/scsi/scsi_lib.c:1196 scsi_setup_fs_cmnd+0xa3/0xb0() Modules linked in: raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx kvm_amd xor kvm snd_hda_codec_realtek raid6_pq snd_hda_intel snd_hda_codec btusb microcode snd_pcm bluetooth edac_core pcspkr serio_raw snd_page_alloc snd_timer snd soundcore rfkill r8169 mii sr_mod cdrom pata_atiixp radeon backlight drm_kms_helper ttm CPU: 1 PID: 160 Comm: kworker/1:1H Not tainted 3.10.0-rc5+ #2 Hardware name: Gigabyte Technology Co., Ltd. GA-MA78GM-S2H/GA-MA78GM-S2H, BIOS F12a 04/23/2010 Workqueue: kblockd blk_delay_work ffffffff81a4499d ffff8801225f5bb8 ffffffff816aeb63 ffff8801225f5bf0 ffffffff810432b0 ffff880123039148 ffff8801233e8b00 ffff8801225f5fd8 ffff880123039148 ffff880123071290 ffff8801225f5c00 ffffffff8104339a Call Trace: [] dump_stack+0x19/0x1b [] warn_slowpath_common+0x70/0xa0 [] warn_slowpath_null+0x1a/0x20 [] scsi_setup_fs_cmnd+0xa3/0xb0 [] sd_prep_fn+0x330/0xf60 [] blk_peek_request+0x13c/0x320 [] scsi_request_fn+0x52/0x540 [] ? blk_delay_work+0x19/0x40 [] __blk_run_queue+0x32/0x40 [] blk_delay_work+0x25/0x40 [] process_one_work+0x211/0x6f0 [] ? process_one_work+0x1a5/0x6f0 [] worker_thread+0x11c/0x390 [] ? process_one_work+0x6f0/0x6f0 [] kthread+0xed/0x100 [] ? insert_kthread_work+0x80/0x80 [] ret_from_fork+0x7c/0xb0 [] ? insert_kthread_work+0x80/0x80 ---[ end trace 22d5bd5ee9fceb9e ]--- 3.9 boots fine, and puts it into recovery mode.. $ cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] md0 : active raid5 sdd1[2] sdb1[0] sdc1[1] 488132608 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU] [>....................] resync = 0.7% (1762712/244066304) finish=73.3min speed=55084K/sec unused devices: -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/