s catastrophic. After 1 hour the tar
> > isn't finish. OK this second client is connect with 100Mbit/s and
> > not on the same switch. But well from 2 min --> ~ 90 min ...:-(
> >
> > I've try for this second client to change on the ZFS-NFS server the
> >
same network switch as the
> server.
>
> I've a second NFS client running FreeBSD 9.1-Stable, and on this second
> client the performance is catastrophic. After 1 hour the tar isn't finish.
> OK this second client is connect with 100Mbit/s and not on the same switch.
> But
;ve try for this second client to change on the ZFS-NFS server the
zfs set sync=disabled
and that change nothing.
On a third NFS client linux (recent Ubuntu) I got the almost same catastrophic
performance. With or without sync=disabled.
Those three NFS client use TCP.
If I do a class
Greetings!
Hopefully I don't get to lost in my explanation here. I have a raid1
array w/ ZFS running ontop of it, yes I realize this isn't the ideal way
to do things, I didn't know that at the time.
The system is stock FreeBSD-8.2-i386, with 2GB of RAM.
In /boot/loader.conf I have the following:
Hi,
I just installed 2 servers with FreeBSD 8.1rc2 and configured block
level replication with HAST and fail-over with ucarp. It works like a
charm, replication is pretty fast (35MB/s on my one disk system) and
fail-over works great.
Now I would like to export some ZFS volumes over NFS (for
Hello People,
I have a webserver with a ZFS pool for storing all the user data. So all the
users have their own filesystem with a quota set. With exporting the system
I ran into some problems with NFS though.
At other machines I can mount the user specific shares resulting in an
80-line fstab per
