On Fri, Dec 18, 2009 at 7:44 PM, Edward Ned Harvey
wrote:
> So ... Something like this?
>
> zpool create -m /path/to/mountpoint myzpool c1t0d0
>
> and then... Assuming it's a 500G disk ...
> zfs create -V 50G /path/to/mountpoint/unused
> zfs create /path/to/mountpoint/importantdata
Once you've c
> I've taken to creating an unmounted empty filesystem with a
> reservation to prevent the zpool from filling up. It gives you
> behavior similar to ufs's reserved blocks.
So ... Something like this?
zpool create -m /path/to/mountpoint myzpool c1t0d0
and then... Assuming it's a 500G disk ...
zf
On Thu, Dec 17, 2009 at 7:11 AM, Edward Ned Harvey
wrote:
> And I've heard a trend of horror stories, that zfs has a tendency to implode
> when it's very full. So try to keep your disks below 90%.
I've taken to creating an unmounted empty filesystem with a
reservation to prevent the zpool from f
> Hi all,
> I need to move a filesystem off of one host and onto another
> smaller
> one. The fs in question, with no compression enabled, is using 1.2 TB
> (refer). I'm hoping that zfs compression will dramatically reduce this
> requirement and allow me to keep the dataset on an 800 GB sto
Jacob Ritorto wrote:
Hi all,
I need to move a filesystem off of one host and onto another smaller
one. The fs in question, with no compression enabled, is using 1.2 TB
(refer). I'm hoping that zfs compression will dramatically reduce this
requirement and allow me to keep the dataset on a
Hi all,
I need to move a filesystem off of one host and onto another smaller
one. The fs in question, with no compression enabled, is using 1.2 TB
(refer). I'm hoping that zfs compression will dramatically reduce this
requirement and allow me to keep the dataset on an 800 GB store. Does
th
