Re: kernel process [nfscl] high cpu

2017-10-15 Thread Rick Macklem
Well, a couple of comments: 1 - I have no idea if NFSv4 mounts (or any NFS mount for that matter) will work correctly within jails. (I don't do jails and know nothing about them. Or, at least very little about them.) 2 - I do know that the "nfsuserd" daemon is badly broken when

Re: kernel process [nfscl] high cpu

2017-10-15 Thread Fabian Freyer
Hi, (I'm not on this list, please CC me in future replies. My apologies to those who get this message twice, I had a typo in the To: header, and have to re-send it to the list.) sorry for reviving such an old thread, but I've run into this problem lately as well, on a 11.1-RELEASE-p1 jailhost

Re: reboot-less zfs volmode property refresh?

2017-10-15 Thread Harry Schmalzbauer
Bezüglich Harry Schmalzbauer's Nachricht vom 15.10.2017 11:57 (localtime): > Bezüglich Harry Schmalzbauer's Nachricht vom 15.10.2017 11:33 (localtime): … >> 3.) Modify existing volmode=dev dataset and write new GPT >> >> zfs set volmode=geom >> hostPsys/bhyveVOL/sys/test

Re: reboot-less zfs volmode property refresh?

2017-10-15 Thread Harry Schmalzbauer
Bezüglich Harry Schmalzbauer's Nachricht vom 15.10.2017 11:33 (localtime): > Hello, > > maybe I'm just missing something obvious, but modifying a dataset's > volmode property seems to force me to reboot the host to have any effect. > > Test to reproduce (parent dataset hostPsys/bhyveVOL/sys has

reboot-less zfs volmode property refresh?

2017-10-15 Thread Harry Schmalzbauer
Hello, maybe I'm just missing something obvious, but modifying a dataset's volmode property seems to force me to reboot the host to have any effect. Test to reproduce (parent dataset hostPsys/bhyveVOL/sys has volmode set ot "dev"): 1.) Create new volume with volmode=geom, and write new GPT