Working + Broken Config below. On a positive note I'm very happy this is working. The performance improvement over a VM using NFS on a virtual 10GBE switch is significant.
Working root@storage1:/main# zfs get all main/zones NAME PROPERTY VALUE SOURCE main/zones type filesystem - main/zones creation Tue Jan 10 4:20 2017 - main/zones used 7.53G - main/zones available 3.71T - main/zones referenced 226M - main/zones compressratio 1.06x - main/zones mounted yes - main/zones quota none default main/zones reservation none default main/zones recordsize 128K default main/zones mountpoint /main/zones default main/zones sharenfs off default main/zones checksum on default main/zones compression lz4 inherited from main main/zones atime on default main/zones devices on default main/zones exec on default main/zones setuid on default main/zones readonly off default main/zones zoned off default main/zones snapdir hidden default main/zones aclmode discard default main/zones aclinherit restricted default main/zones canmount on default main/zones xattr on default main/zones copies 1 default main/zones version 5 - main/zones utf8only off - main/zones normalization none - main/zones casesensitivity sensitive - main/zones vscan off default main/zones nbmand off default main/zones sharesmb off default main/zones refquota none default main/zones refreservation none default main/zones primarycache all default main/zones secondarycache all default main/zones usedbysnapshots 0 - main/zones usedbydataset 226M - main/zones usedbychildren 7.31G - main/zones usedbyrefreservation 0 - main/zones logbias latency default main/zones dedup off default main/zones mlslabel none default main/zones sync standard default main/zones refcompressratio 2.05x - main/zones written 226M - main/zones logicalused 7.96G - main/zones logicalreferenced 463M - main/zones filesystem_limit none default main/zones snapshot_limit none default main/zones filesystem_count none default main/zones snapshot_count none default main/zones redundant_metadata all default root@storage1:/main# /usr/bin/ls -lV zones/ total 2 drwxr-xr-x 2 root root 3 Jan 10 04:20 images owner@:rwxp-DaARWcCos:-------:allow group@:r-x---a-R-c--s:-------:allow everyone@:r-x---a-R-c--s:-------:allow drwx------ 4 root root 5 Jan 10 13:20 lx0 owner@:rwxp-DaARWcCos:-------:allow group@:------a-R-c--s:-------:allow everyone@:------a-R-c--s:-------:allow Broken root@storage1:/main# zfs get all main/zones NAME PROPERTY VALUE SOURCE main/zones type filesystem - main/zones creation Tue Jan 10 13:57 2017 - main/zones used 226M - main/zones available 3.71T - main/zones referenced 226M - main/zones compressratio 2.05x - main/zones mounted yes - main/zones quota none default main/zones reservation none default main/zones recordsize 128K default main/zones mountpoint /main/zones default main/zones sharenfs off default main/zones checksum on default main/zones compression lz4 inherited from main main/zones atime off local main/zones devices on default main/zones exec on default main/zones setuid on default main/zones readonly off default main/zones zoned off default main/zones snapdir hidden local main/zones aclmode passthrough local main/zones aclinherit passthrough local main/zones canmount on default main/zones xattr on default main/zones copies 1 default main/zones version 5 - main/zones utf8only on - main/zones normalization formD - main/zones casesensitivity insensitive - main/zones vscan off default main/zones nbmand on local main/zones sharesmb off local main/zones refquota none default main/zones refreservation none default main/zones primarycache all default main/zones secondarycache all default main/zones usedbysnapshots 0 - main/zones usedbydataset 226M - main/zones usedbychildren 0 - main/zones usedbyrefreservation 0 - main/zones logbias latency default main/zones dedup off default main/zones mlslabel none default main/zones sync standard default main/zones refcompressratio 2.05x - main/zones written 226M - main/zones logicalused 463M - main/zones logicalreferenced 463M - main/zones filesystem_limit none default main/zones snapshot_limit none default main/zones filesystem_count none default main/zones snapshot_count none default main/zones redundant_metadata all default root@storage1:/main# /usr/bin/ls -lV ./zones/ total 1 drwxrwxrwx+ 2 root root 3 Jan 10 13:57 images user:root:rwxpdDaARWcCos:fd----I:allow everyone@:rwxpdDaARWc--s:fd----I:allow owner@:rwxp-DaARWcCos:-------:allow group@:r-x---a-R-c--s:-------:allow everyone@:r-x---a-R-c--s:-------:allow On Tue, Jan 10, 2017 at 5:40 AM, Илья Кулагин <k...@kiv.pp.ru> wrote: > Hi all. > > 1st, it seems to me that it is necessary for all lx-users to > find/share/explain some common steps to debug software misbehaviour in lx > zone. Because for my (very small, of course) practice, linux software often > is based on strange assumptions and even 'dirty hacks'. > Maybe with dtrace, like it was done for 'unimplemented syscalls' in > SmartOS wiki https://wiki.smartos.org/display/DOC/LX+Branded+Zones# > LXBrandedZones-huntingforunsupportedsyscalls > Maybe whatelse... > > So i have reproducible steps and also solve my problem. > > If I create my dataset via napp-it. It seems like it applies special > permissions. LX will complain that other and group should not have write > permissions on the zone directory. So I remove these via chmod o-w and > chmod g-w. > > > I think that in this case it will be useful that you compare full zfs > properties list (`zfs get all ` for zone root) and full acls (`/usr/bin/ls > -lV ` -- of course, issued from host with zone running to display actual > permissions while FS is mounted) for both zones - working and crashing ones. > > > At this point I can create the zone and in doing so I can reproduce the > error. If I create the data set with your standard zfs create tank/zones > the permissions are fine by default and the bug is not reproducible. > > So somehow somewhere whatever is happening underneath the hood is > sensitive to these permissions on the second write in this program. > > Strange indeed. > > On Mon, Jan 9, 2017 at 10:03 PM, Dan McDonald <dan...@omniti.com> wrote: > >> >> > On Jan 9, 2017, at 10:01 PM, Mini Trader <miniflowtra...@gmail.com> >> wrote: >> > >> > Just to reiterate on a fresh install of 20 I got no error. Different >> hardware too. >> >> WEIRD. (Sorry I didn't catch that earlier. Juggling other balls >> concurrently!) >> >> Okay, thanks for the update. Not sure if there's anything I can do in >> the immediate term, but thanks for keeping me informed (and giving me the >> full zonecfg). >> >> Thanks! >> Dan >> >> > > > _______________________________________________ > OmniOS-discuss mailing > listOmniOS-discuss@lists.omniti.comhttp://lists.omniti.com/mailman/listinfo/omnios-discuss > > > -- > С уважением, Илья Кулагин > > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss@lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > >
_______________________________________________ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss