Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 16 Mar 2002 22:10:58 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 16 Mar 2002 22:10:49 -0500 Received: from lightning.swansea.linux.org.uk ([194.168.151.1]:19214 "EHLO the-village.bc.nu") by vger.kernel.org with ESMTP id ; Sat, 16 Mar 2002 22:10:36 -0500 Subject: Re: /dev/md0: Device or resource busy To: dean-list-linux-kernel@arctic.org (dean gaudet) Date: Sun, 17 Mar 2002 03:26:31 +0000 (GMT) Cc: linux-kernel@vger.kernel.org In-Reply-To: from "dean gaudet" at Mar 16, 2002 05:44:04 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > i have 3 other md devices which i can stop no problem (even with 0xfd > autodetection), just not /dev/md0. > > % raidstop /dev/md0 > /dev/md0: Device or resource busy > > i don't have any filesystem mounted on md0, and "lsof | grep md" doesn't > show anything. lsof isnt always the most reliable to tools if a kernel thread or nfs ran off with it. Is md0 doing anything else - like rebuilding. Is there anything that has been triggered or run from it - paticularly kernel threads - 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/