On 4 dec 2009, at 18.47, Cindy Swearingen wrote:
Hi--
The problem with your test below was creating a pool by using the
components from another pool. This configuration is not supported.
We don't have a lot of a specific information about using volumes,
other than for using as iSCSI and
Hi--
The problem with your test below was creating a pool by using the
components from another pool. This configuration is not supported.
We don't have a lot of a specific information about using volumes,
other than for using as iSCSI and COMSTAR devices.
You might review our ZFS best
Hi Ragnar,
A bug might exist but you are building a pool based on the ZFS
volumes that are created in another pool. This configuration
is not supported and possible deadlocks can occur.
If you can retry this example without building a pool on another
pool, like using files to create a pool and
Thank you Cindy for your reply!
On 3 dec 2009, at 18.35, Cindy Swearingen wrote:
A bug might exist but you are building a pool based on the ZFS
volumes that are created in another pool. This configuration
is not supported and possible deadlocks can occur.
I had absolutely no idea that ZFS
It seems that device names aren't always updated when importing
pools if devices have moved. I am not sure if this is only an
cosmetic issue or if it could actually be a real problem -
could it lead to the device not being found at a later import?
/ragge
(This is on snv_127.)
I ran the
