Unfortunately, since we got a new priority on the project, I had to scrap and
recreate the pool, so I don't have any of the information anymore.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://
John wrote:
I was able to solve it, but it actually worried me more than anything.
Basically, I had created the second pool using the mirror as a primary device.
So three disks but two full disk root mirrors.
Shouldn't zpool have detected an active pool and prevented this? The other LDOM
was
Hi John,
In general, ZFS will warn you when you attempt to add a device that
is already part of an existing pool. One exception is when the system
is being re-installed.
I'd like to see the set of steps that led to the notification failure.
Thanks,
Cindy
On 01/19/10 20:58, John wrote:
I was
I was able to solve it, but it actually worried me more than anything.
Basically, I had created the second pool using the mirror as a primary device.
So three disks but two full disk root mirrors.
Shouldn't zpool have detected an active pool and prevented this? The other LDOM
was claiming a cor
Hi John,
The message below is a ZFS message, but its not enough to figure out
what is going on in an LDOM environment. I don't know of any LDOMs
experts that hang out on this list so you might post this on the
ldoms-discuss list, if only to get some more troubleshooting data.
I think you are say
I've got an LDOM that has raw disks exported through redundant service domains
from a J4400. Actually, I've got seven of these LDOM's. On Friday, we had to
power the rack down for UPS maintenance. We gracefully shutdown all the Solaris
instances, waited about 15 min, then powered down the storag
