That is correct I am on 151020 just moved up from LTS for this feature.
Just to be clear about one thing.
If you run this on a regular directory in the LX zone there is no issue. It
only takes place if the directory being read is from the LOFS mount of a
ZFS dataset. My mount has a property of re
Thank you. I've discussed with Joyent, and they couldn't reproduce it. They
have a fix we don't, so between that and whether or not it's fixed on bloody
(you're on r151020, right mini?), I'll have to try it myself. It's possible
the Joyent fix (outside LX, not yet upstreamed) may cure what ai
1. Does not happen on native.
2. My non-global zones are under /tank/zones/
3. It uses python - but the calls are all stdlib calls, no magic they are
going directly to C. You can reproduce with same calls on C the system
will eventually return ENOENT/ERRNO=2.
4. Looks to be LX specific. I also te
Thank you for doing this! Some questions in-line:
> On Jan 16, 2017, at 10:40 AM, Mini Trader wrote:
>
> I spent a bit of time yesterday using dtrace and looking at the source. I
> believe I found why the system is falsely reporting that the current
> directory does not exist and have create
I spent a bit of time yesterday using dtrace and looking at the source. I
believe I found why the system is falsely reporting that the current
directory does not exist and have created a simple program to reproduce the
problem. The problem seems to be related to when v_path in the vnode
struct go
