Podlipnik wrote:
When creating raidz pool out of n disks where n =>2 pool size will get a size
of the smallest disk multiplied by n:
# zpool create -f newpool raidz c1t12d0 c1t10d0 c1t13d0
# zpool list
NAMESIZEUSED AVAILCAP HEALTH ALTROOT
newpool
> Excuse me if I'm mistaken, but I think the question is on the lines of how
to access and more importantly - Backup zfs pools/filesystems present on a
system by just booting from a CD/DVD.
>
> I think the answer would be on the lines of (forced?) importing of zfs
pools
> present on the system and
> Dennis,
> i'm not sure if this will help you, but i had something similar happen and
> was able to get my zpool back.
>
> i decided to install (not upgrade) Nevada snv-51 which was the current build
> at the time. I had (and thankfully still have) a zpool which i'd created
> under snv-37 on a se
I should perhaps note that my last email on delegation describes the
optimisations possible under the NFSv4 protocol, as per RFC, all of
which are not necessarily implemented in our own Solaris client.
In particular, I think that fsync and committed writes do still go
through to the server, so
When creating raidz pool out of n disks where n =>2 pool size will get a size
of the smallest disk multiplied by n:
# zpool create -f newpool raidz c1t12d0 c1t10d0 c1t13d0
# zpool list
NAMESIZEUSED AVAILCAP HEALTH ALTROOT
newpool 139G141K1
This thread started with the notion that ZFS provided a
very bad NFS service to the point of > 10X degradation over
say UFS. What I hope we have an agreement on, is that these
scale of performance difference does not come from ZFS but
from an NFS service that would sacrifice integrity. Enabling
t
