[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20061203234202.GL7114@grifter.jdc.home>
Date: Sun, 3 Dec 2006 18:42:02 -0500
From: Jim Crilly <jim@....dont.jablowme.net>
To: Tomasz Chmielewski <mangoo@...g.org>
Cc: Ross Vandegrift <ross@...listi.us>,
Andreas Schwab <schwab@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: why can't I remove a kernel module (or: what uses a given module)?
On 12/03/06 08:59:10PM +0100, Tomasz Chmielewski wrote:
> Ross Vandegrift wrote:
> >On Sun, Dec 03, 2006 at 12:58:24PM +0100, Tomasz Chmielewski wrote:
> >>You mean the "Used by" column? No, it's not used by any other module
> >>according to lsmod output.
> >>
> >>Any other methods of checking what uses /dev/sda*?
> >
> >There's a good chance that if it was loaded at system boot, hald or
> >udev may be doing something with it.
>
> This machine doesn't have hal; when I kill udevd still doesn't help.
>
> Yes, something's using that drive, be it a program, a module (unlikely),
> or something that is compiled directly in the kernel (for example,
> md/raid1).
> But what is it?
>
> Kernel knows it, as it refuses to remove the module (via rmmod), but how
> to tell kernel to share this knowledge with me?
>
Have you checked to make sure there's no swap partitions on it being
automatically activated at boot? Also, have you checked the output of lsof?
Jim.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists