Hi Dan,
It's the following open call that failed:
23724: open("/dev/overlay", O_RDWR|O_EXCL) Err#2 ENOENT
For some reason 'add_drv overlay' didn't load the driver successfully.
Running rem_drv and then add_drv resolved the issue. After that, I rebooted
the host several times,
> On May 18, 2018, at 5:11 PM, Youzhong Yang wrote:
>
> Thanks Jason. In my environment, I've disabled KPTI through boot var
> 'kpti=0', not sure if it contributes to the issue.
kpti shouldn't affect anything.
Could you:
1.) ```truss -f -o /tmp/truss-out.txt
Thanks Jason. In my environment, I've disabled KPTI through boot var
'kpti=0', not sure if it contributes to the issue.
On Fri, May 18, 2018 at 5:06 PM, Jason King
wrote:
> I’m building an image from this commit and will get it loaded on a test
> Triton setup. I’ll
I’m building an image from this commit and will get it loaded on a test
Triton setup. I’ll update the list once I’ve figured out what’s going on.
From: Youzhong Yang
Reply: smartos-discuss@lists.smartos.org
illumos-joyent: OS-6963 add_fbuf should also use is_env_string
smartos-live: OS-6958 bad comparison introduced with OS-6630
On Fri, May 18, 2018 at 4:11 PM, Jason King
wrote:
> What is the last commit in your branch that you built? I’ll try to
> recreate this
What is the last commit in your branch that you built? I’ll try to
recreate this locally.
From: Youzhong Yang
Reply: smartos-discuss@lists.smartos.org
Date: May 18, 2018 at 3:04:31
Hi,
Today I built SmartOS from the master branch. After rebooting the server,
varpd did not start up:
# svcs varpd
STATE STIMEFMRI
maintenance15:53:23 svc:/network/varpd:default
# tail /var/svc/log/network-varpd\:default.log
[ May 18 15:53:23 Executing start method