Hi Richard,
> The consensus best
> practice is to have enough RAM that you don't need to
> swap. If you need to
> swap, your life will be sad no matter what your disk
> config is.
>From my understanding Solaris does not overcommit memory allocation, so every
>allocation must be backed by some f
Hi,
my main interest is sharing a zpool between machines, so the zfs filesystems on
different hosts can share a single lun. When you run several applications each
in a different zone and allow the zones to be run on one of several hosts
individually (!) this currently means at least one separat
Hi Torrey,
> On 1/15/07, Torrey McMahon <[EMAIL PROTECTED]>
> wrote:
> What you will find is that while you can mount the
> UFS (ZFS should
> prevent mounting but that's another story), any
> updates on previously
> read files will not be visible.
Actually it's quite worth with UFS: mounting a fi
Hello Nate,
> > I have few issues about ZFS and virtualization:
> >
> > [b]Virtualization and performance[/b]
> > When filesystem traffic occurs on a zpool
> containing
> > only spindles dedicated to this zpool i/o can be
> > distributed evenly. When the zpool is located on a
> > lun sliced from a
Hi Constantin,
> The basic problem with regular snapshotting is that you end up managing so
> many of them. Wouldn't it be nice if you could assign an expiration date to a
> snapshot?
The only reason you want the snapshot removed is because you don't want your
pool to become full. IIRC VxFS has
Hi experts,
I have few issues about ZFS and virtualization:
[b]Virtualization and performance[/b]
When filesystem traffic occurs on a zpool containing only spindles dedicated to
this zpool i/o can be distributed evenly. When the zpool is located on a lun
sliced from a raid group shared by multi
