OK, got it : just use zpool import.
Sorry for the inconvenience ;-)
C.
-Message d'origine-
De : zfs-discuss-boun...@opensolaris.org
[mailto:zfs-discuss-boun...@opensolaris.org] De la part de Cyril Payet
Envoyé : mardi 6 janvier 2009 09:16
À : D. Eckert; zfs-discuss@opensolaris.org
Btw,
When you import a pool, you must know its name.
Is there any command to get the pool name to whom a non-impoted disks belongs.
"# vxdisk -o alldgs list "does this with vxm.
Thanx for your replies.
C.
-Message d'origine-
De : zfs-discuss-boun...@opensolaris.org
[mailto:zfs-discuss-bo
ks" to make the HDS-Frame able to
reclaime these ones ? I know that this will create some overhead...
It might leads to a smaller "block allocation history" but could be very
usefull for zero-pages-reclaim.
I do hope that my question was clear enough...
Thanx
Hello there,
I just wonder how to make zfs aware of a lun resizing, with no downtime
(Veritas "vxdisk resize" or MS "diskpart" can do this).
I'm quite sure that there were some threads on this but I can't find
them.
I do know that resizing a lun is not the common way to expand a pool
(since a simpl
Title: test2
Hi there,
I need to migrate zfs data from a huge vdev
to a
smaller one, as only 5% of the first vdev is used.
Many zfs items were created on the source vdev, organized as tree,
subtrees,
etc.
zpool attach and detach won't help here as the target device is
smaller than the source
_
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
--
Resent, for Fred...
Hi gurus,
When creating some small files an ZFS directory, used blocks number is
not what could be espected:
hinano# zfs list
NAME USED AVAIL REFER MOUNTPOINT
pool2 702K 16.5G 26.5K /pool2
pool2/new 604K 16.5G34K /po
