I just copied a snapshot from one zpool (let's call is "source") to
another one ("destination") on the same machine using zpool send/recv.
I'm wondering why this process is taking so much bandwidth reading from
"destination", while writing to it, or reading from "source" did not?
At least this is w
On Sat, 2010-08-14 at 17:35 +0200, Andrej Podzimek wrote:
> > 3. Just stick with b134. Actually, I've managed to compile my way up to
> > b142, but I'm having trouble getting beyond it - my attempts to install
> > later versions just result in new boot environments with the old kernel,
> > even
I'm not sure about the right naming, but here is what I did and what my
problem is now:
I imported a "syspool" as another name (that's why I use the naming
"alias"), using the following command: zpool import -f syspool original
My problem is that after reboot, the syspool is available both as
"sys
Tim Cook wrote:
>
>
> On Sun, Jan 3, 2010 at 6:58 PM, Jerome Warnier <mailto:jwarn...@beeznest.net>> wrote:
>
> Hi,
>
> I'm "smbsharing" ZFS filesystems.
> I know how to restrict access to it to some hosts (and users), but did
>
Hi,
I'm "smbsharing" ZFS filesystems.
I know how to restrict access to it to some hosts (and users), but did
not find any way to forbid the smb protocol being advertised on a
specific interface (or the other way around, specify the ones I agree with).
Is there any other way than setting up a firew
