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. The structure looks like this

data1                  208K  8.03T  24.5K  /data1
data1/zones            103K  8.03T  29.5K  /zones
data1/zones/mytest    24.5K  8.03T  24.5K  /zones/mytest

Anyway, I then create a new sparse zone with the root in
/zones/mytest. It looks like this (just a barebone setup)

# zonecfg -z mytest
zonecfg:mytest> info
zonename: mytest
zonepath: /zones/mytest
autoboot: false
pool:
limitpriv:
inherit-pkg-dir:
       dir: /lib
inherit-pkg-dir:
       dir: /platform
inherit-pkg-dir:
       dir: /sbin
inherit-pkg-dir:
       dir: /usr

When I execute zoneadm -z mytest install I get the following error:

# zoneadm -z mytest install
zoneadm: /zones/mytest: Value too large for defined data type
could not verify zonepath /zones/mytest because of the above errors.
zoneadm: zone mytest failed to verify

Is this due to a too large filesystem or something like this? Sure,
8TB is quite big but not that large by todays standard (and yes, we
really want an 8TB filesystem here. it is not a production system).

If I look at the truss output it looks like a call to statvfs()
returns EOVERFLOW which probably isn't a good thing.

resolvepath("/zones/mytest", "/zones/mytest", 1024) = 13
stat("/zones/mytest", 0xFFBFE870)               = 0
open("/etc/zones/index", O_RDONLY)              = 5
fstat64(5, 0xFFBFC928)                          = 0
fstat64(5, 0xFFBFC7D0)                          = 0
ioctl(5, TCGETA, 0xFFBFC8B4)                    Err#25 ENOTTY
read(5, " #   C o p y r i g h t  ".., 8192)     = 398
read(5, 0x0005942C, 8192)                       = 0
llseek(5, 0, SEEK_CUR)                          = 398
close(5)                                        = 0
resolvepath("/zones/mytest/..", "/zones", 1024) = 6
stat("/zones", 0xFFBFE870)                      = 0
statvfs("/zones/mytest", 0xFFBFDFD4)            Err#79 EOVERFLOW
fstat64(2, 0xFFBFCC80)                          = 0
zoneadmwrite(2, " z o n e a d m", 7)                    = 7
: write(2, " :  ", 2)                           = 2
/zones/mytestwrite(2, " / z o n e s / m y t e s".., 13) = 13
: write(2, " :  ", 2)                           = 2
Value too large for defined data typewrite(2, " V a l u e   t o o   l
a".., 37) = 37

write(2, "\n", 1)                               = 1
could not verify zonepath write(2, " c o u l d   n o t   v e".., 26)    = 26
/zones/mytestwrite(2, " / z o n e s / m y t e s".., 13) = 13
because of the above errors.
write(2, "   b e c a u s e   o f  ".., 30)      = 30
stat("/lib", 0xFFBFDC5C)                        = 0
stat("/platform", 0xFFBFDC5C)                   = 0
stat("/sbin", 0xFFBFDC5C)                       = 0
stat("/usr", 0xFFBFDC5C)                        = 0
zoneadmwrite(2, " z o n e a d m", 7)                    = 7
: zone write(2, " :   z o n e  ", 7)                    = 7
mytestwrite(2, " m y t e s t", 6)                       = 6
failed to verify
write(2, "   f a i l e d   t o   v".., 18)      = 18
_exit(1)

Is there a solution here but to move the zone root to a smaller disk?

cheers,
Nickus
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org

Reply via email to