On 4/3/07, Matthew Ahrens [EMAIL PROTECTED] wrote:
You can work around this by setting the quota on an ancestor of the
to-be-created clone. Also, implementing RFE 6364688 method to preserve
properties when making a clone would make workaround #1 (set a quota on
the first fs) work for the
Niclas Sodergard wrote:
On 3/29/07, Ed Plese [EMAIL PROTECTED] wrote:
Is there a solution here but to move the zone root to a smaller disk?
Set a quota (10G should work just fine) on the filesystem and then
perform the zone install. Afterwards remove the quota.
Thanks, seems to work just
On 3/30/07, Frank Cusack [EMAIL PROTECTED] wrote:
On March 29, 2007 1:18:31 PM +0300 Niclas Sodergard [EMAIL PROTECTED]
wrote:
Anyway, I then create a new sparse zone with the root in
/zones/mytest. It looks like this (just a barebone setup)
I thought zone root on zfs was not supported.
Not
Hi everyone,
Sorry for crossposting but it seems I have stumbled upon a problem
that affects both. I have a V490 running Solaris 10u3 with a 16x750GB
raid array connected to it. I've created an 8TB zfs filesystem called
data1 and created a zfs filesystem called data1/zones mounted to
/zones.
On Thu, Mar 29, 2007 at 01:18:31PM +0300, Niclas Sodergard wrote:
Sorry for crossposting but it seems I have stumbled upon a problem
that affects both. I have a V490 running Solaris 10u3 with a 16x750GB
raid array connected to it. I've created an 8TB zfs filesystem called
data1 and created a
On 3/29/07, Ed Plese [EMAIL PROTECTED] wrote:
Is there a solution here but to move the zone root to a smaller disk?
Set a quota (10G should work just fine) on the filesystem and then
perform the zone install. Afterwards remove the quota.
Thanks, seems to work just fine. It solved my
On March 29, 2007 1:18:31 PM +0300 Niclas Sodergard [EMAIL PROTECTED]
wrote:
Anyway, I then create a new sparse zone with the root in
/zones/mytest. It looks like this (just a barebone setup)
I thought zone root on zfs was not supported.
-frank
___
