yes I am an experienced Solaris admin and know all about devfsadm :-)
and the older disks command.

It doesn't help in this case.  I think it's a BIOS thing.  Linux and
Windows can't see IDE drives that aren't there at boot time either,
and on Solaris the SATA controller runs in some legacy mode so I guess
that's why you can't see the newly added drive.

Unfortunately all my x2100 hardware is in production and I can't
readily retest this to verify.

-frank

On January 23, 2007 12:02:48 PM +0700 Peter Karlsson <[EMAIL PROTECTED]> wrote:
Hi Frank,

try man devfsadm, it will update devfs with your new disk drives. disks
is an older command that does about the same thing.

Cheers,
Peter

Frank Cusack wrote:
On January 22, 2007 12:12:19 PM -0600 Brian Hechinger
<[EMAIL PROTECTED]> wrote:
On Mon, Jan 22, 2007 at 09:39:19AM -0800, Frank Cusack wrote:
On January 21, 2007 12:15:22 AM -0200 Toby Thain <[EMAIL PROTECTED]>
wrote:
> To be clear: the X2100 drives are neither "hotswap" nor "hotplug"
under
> Solaris. Replacing a failed drive requires a reboot.

Also, adding a drive that wasn't present at boot requires a reboot.

This couldn't possibly be true, unless we've taken major steps backwards
as this has always been possible (at least on sparc)

It is true.  Try it.

[Sorry to send a reply to a personal mail back to the list, but your
email address bounces

450 <[EMAIL PROTECTED]>: Recipient address rejected: Domain
not found]

-frank
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss




_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to