All of lore.kernel.org
 help / color / mirror / Atom feed
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, 15 Aug 2006 21:55:26 +0900	[thread overview]
Message-ID: <44E1C43E.1020302@gmail.com> (raw)
In-Reply-To: <44E105A7.3030900@grokthis.net>

Eric Windisch wrote:
> First, I should note that I've attempted to use the latest 
> libata-tj-stable patch, against 2.6.17.4 and 2.6.17.7 (it patched 
> cleanly), and I've tried 2.6.18-rc3.  All three have given me either the 
> same, or a worse result.  My controller is a sil3124, I have 5 sata 
> drives, and I'm using a couple sil 3726 PMPs (to support a potential 
> maximum of 12 drives with my Norco 1220 disk array).
> 
> Regarding the behavior, while I can see all 5 disks, and even partition 
> them (iirc, parted worked, but fdisk didn't), and see my created 
> partitions, when attempting to use 'mdadm --create', I get the error:  
> "Device or resource busy".   mkfs.ext3 gives a similar error as well.  
> The disks are not mounted or otherwise being accessed (such as via 
> software raid or lvm).

Hello, Eric.

Can you post the result of 'dmesg', 'cat /proc/mounts' and 'fuser -v 
/dev/sdX#'?

-- 
tejun

  reply	other threads:[~2006-08-15 12:55 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 [this message]
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
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=44E1C43E.1020302@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.