public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tobias Oed <tobiasoed@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: why can't I remove a kernel module (or: what uses a given module)?
Date: Mon, 04 Dec 2006 11:10:01 +0100	[thread overview]
Message-ID: <el0s6r$agu$1@sea.gmane.org> (raw)
In-Reply-To: 45732C8E.4060801@wpkg.org

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?

Since you mention md, dm comes to mind. I have seen a couple of drives that
were previously attached to fake raid controllers becoming unavailable when
moved to a normal controller. I haven't found the one size workaround for
the problem yet. Can you check
/sys/block/sda/holders ?
Also /sys/bus/ide/whoevertheholderis/[bind|unbind] are 'curious' but I'm not
sure how one is supposed to use them.
Tobias




  parent reply	other threads:[~2006-12-04 10:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-03 11:20 why can't I remove a kernel module (or: what uses a given module)? Tomasz Chmielewski
2006-12-03 11:34 ` Andreas Schwab
2006-12-03 11:58   ` Tomasz Chmielewski
2006-12-03 15:49     ` Ross Vandegrift
2006-12-03 19:59       ` Tomasz Chmielewski
2006-12-03 23:42         ` Jim Crilly
2006-12-04  8:02           ` Tomasz Chmielewski
2006-12-04 10:10         ` Tobias Oed [this message]
2006-12-04 10:39           ` Tomasz Chmielewski
2006-12-05  0:15           ` Michal Jaegermann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='el0s6r$agu$1@sea.gmane.org' \
    --to=tobiasoed@hotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox