<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi all.<br>
<br>
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'.<br>
Maybe with dtrace, like it was done for 'unimplemented syscalls' in
SmartOS wiki
<a class="moz-txt-link-freetext" href="https://wiki.smartos.org/display/DOC/LX+Branded+Zones#LXBrandedZones-huntingforunsupportedsyscalls">https://wiki.smartos.org/display/DOC/LX+Branded+Zones#LXBrandedZones-huntingforunsupportedsyscalls</a><br>
Maybe whatelse...<br>
<br>
<blockquote
cite="mid:CACFEqht-PrwzCNWy0EaCRteXT9QhUOiUHKMvMX35KJXNJKhD7g@mail.gmail.com"
type="cite">
<div dir="ltr">So i have reproducible steps and also solve my
problem.
<div><br>
</div>
<div>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.</div>
</div>
</blockquote>
<br>
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.<br>
<br>
<blockquote
cite="mid:CACFEqht-PrwzCNWy0EaCRteXT9QhUOiUHKMvMX35KJXNJKhD7g@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>So somehow somewhere whatever is happening underneath the
hood is sensitive to these permissions on the second write in
this program.</div>
<div><br>
</div>
<div>Strange indeed.</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Jan 9, 2017 at 10:03 PM, Dan
McDonald <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:danmcd@omniti.com" target="_blank">danmcd@omniti.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class=""><br>
> On Jan 9, 2017, at 10:01 PM, Mini Trader <<a
moz-do-not-send="true"
href="mailto:miniflowtrader@gmail.com">miniflowtrader@gmail.com</a>>
wrote:<br>
><br>
> Just to reiterate on a fresh install of 20 I got no
error. Different hardware too.<br>
<br>
</span>WEIRD. (Sorry I didn't catch that earlier. Juggling
other balls concurrently!)<br>
<br>
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).<br>
<br>
Thanks!<br>
<span class="HOEnZb"><font color="#888888">Dan<br>
<br>
</font></span></blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OmniOS-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OmniOS-discuss@lists.omniti.com">OmniOS-discuss@lists.omniti.com</a>
<a class="moz-txt-link-freetext" href="http://lists.omniti.com/mailman/listinfo/omnios-discuss">http://lists.omniti.com/mailman/listinfo/omnios-discuss</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
С уважением, Илья Кулагин</pre>
</body>
</html>