From: "Scott T. Smith" <scott@gelatinous.com>
To: linux-raid@vger.kernel.org
Subject: 3ware drive hotswapping
Date: Mon, 21 Jun 2004 18:05:57 -0700 [thread overview]
Message-ID: <1087866357.8757.98.camel@tinny.home.foo> (raw)
I'm testing the ability of a 3ware 8506 card to hotswap SATA drives in
JBOD mode, and I'm having problems.
When I remove the drive, the device becomes inaccessible -- that's
obvious. However, when I reinsert the drive, I can't access it. I've
tried echoing 'scsi remove-single-device W X Y Z' followed by 'scsi
add-single-device W X Y Z'; the remove causes the /dev/sd* devices to
disappear, but the add does not create any /dev/sd* entries (I'm using
devfs -- though trying to access the devices through a mknod'd block
device doesn't help either).
What is the correct procedure to get a 2.6 kernel to integrate drives?
Scott
next reply other threads:[~2004-06-22 1:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 1:05 Scott T. Smith [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-22 1:17 3ware drive hotswapping Adam Radford
2004-06-22 1:20 ` Scott T. Smith
2004-06-22 3:36 ` Scott T. Smith
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=1087866357.8757.98.camel@tinny.home.foo \
--to=scott@gelatinous.com \
--cc=linux-raid@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