From: Tejun Heo <htejun@gmail.com>
To: Eric Windisch <eric@grokthis.net>
Cc: linux-ide@vger.kernel.org
Subject: Re: Libata-tj-stable patch /w sil3124 and PMP... 'device or resource busy'
Date: Tue, 29 Aug 2006 23:57:06 +0900 [thread overview]
Message-ID: <44F455C2.1010309@gmail.com> (raw)
In-Reply-To: <1156863511.3718.36.camel@manet>
Eric Windisch wrote:
>> The exclusive refs held above are never released. Thus the kernel
>> correctly denies any other exclusive access to the devices. dm is
>> holding them all. I have never used dm so don't know much about it. It
>> seems that you'll have to make dm ignore those SCSI disks if you wanna
>> use them for any other purpose.
>
> I've never used it either, at least not directly. Whatever it is doing
> is automatic. However, you're right, I'm sorry for bringing up someone
> else's bug -- if nothing else, its good google fodder ;-) So far, its
> looking to me like a bug in Ubuntu Dapper.
Maybe you're supposed to use all disks via dm, which actually makes
sense. Direct partitions on disks are pretty lame way to manage disks
these days although I've never used anything else. :-p
> I haven't yet figured out
> how to tell Ubuntu to leave my devices alone (yes, I looked at udev),
> but at least I can get my disks working!
>
> $ dmsetup remove sde1
> root@san001:~# mkfs.ext3 -m1 /dev/sde1 2>/dev/null >/dev/null && echo 1
> 1
Great.
--
tejun
next prev parent reply other threads:[~2006-08-29 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 23:22 Libata-tj-stable patch /w sil3124 and PMP... 'device or resource busy' Eric Windisch
2006-08-15 12:55 ` Tejun Heo
2006-08-16 2:29 ` Eric Windisch
2006-08-27 9:35 ` Tejun Heo
2006-08-28 1:16 ` Eric Windisch
2006-08-29 2:55 ` Tejun Heo
2006-08-29 14:58 ` Eric Windisch
2006-08-29 14:57 ` Tejun Heo [this message]
2006-08-29 15:15 ` Eric Windisch
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=44F455C2.1010309@gmail.com \
--to=htejun@gmail.com \
--cc=eric@grokthis.net \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).