Date: Mon, 18 Jan 2021 12:27:10 -0500 From: J David <j.david.lists@gmail.com> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: Konstantin Belousov <kostikbel@gmail.com>, "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: Re: Major issues with nfsv4 Message-ID: <CABXB=RRR_WVLxV-tUcSpu2jHm_AQXPAO-yfKDH64=T-bsHOXFQ@mail.gmail.com> In-Reply-To: <YQXPR0101MB096854F3CB5423CB485BEDB1DDA50@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM> References: <YQXPR0101MB096849ADF24051F7479E565CDDCA0@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM> <CABXB=RSyN%2Bo2yXcpmYw8sCSUUDhN-w28Vu9v_cCWa-2=pLZmHg@mail.gmail.com> <YQXPR0101MB09680D155B6D685442B5E25EDDCA0@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM> <CABXB=RSSE=yOwgOXsnbEYPqiWk5K5NfzLY=D%2BN9mXdVn%2B--qLQ@mail.gmail.com> <YQXPR0101MB0968B17010B3B36C8C41FDE1DDC90@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM> <X9Q9GAhNHbXGbKy7@kib.kiev.ua> <YQXPR0101MB0968C7629D57CA21319E50C2DDC90@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM> <X9UDArKjUqJVS035@kib.kiev.ua> <CABXB=RRNnW9nNhFCJS1evNUTEX9LNnzyf2gOmZHHGkzAoQxbPw@mail.gmail.com> <YQXPR0101MB0968B120A417AF69CEBB6A12DDC80@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM> <X9aGwshgh7Cwiv8p@kib.kiev.ua> <CABXB=RTFSAEZvp%2BmoiF%2BrE9vpEjJVacLYa6G=yP641f9oHJ1zw@mail.gmail.com> <YQXPR0101MB09681D2CB8FBD5DDE907D5A5DDC40@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM> <CABXB=RTLogtoFi%2BtAyUHii%2BWFCQtj1qFjbiz2CQC8whNYEBy2Q@mail.gmail.com> <YQXPR0101MB0968C6331C1C1F33E18523C2DDA80@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM> <CABXB=RQG_hR%2BVzC2mSiwK-9h8sEAQA5xrx2tjiKsPngoOMqxFQ@mail.gmail.com> <YQXPR0101MB0968F66CC35FFAD5767929FFDDA60@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM> <CABXB=RT08WUVy6dqcDwE9BDER4P79_h6zbTjsjoTV%2BrT4WiNBg@mail.gmail.com> <YQXPR0101MB096854F3CB5423CB485BEDB1DDA50@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
Using oneopenown in even limited testing seems to cause NFS mounts to completely hang (requiring "umount -N") on a fairly regular basis. The problems without oneopenown are worse than that it will "eventually constipate the mount." There also seems to be some sort of garbage collection or something that occurs periodically that causes one nfscl process to jump to 100% CPU and create systemwide disruption, causing delay in many unrelated system calls (30+ second delays observed in at least fork, systemctl, and ioctl via ktrace of processes that do not touch any NFS filesystem). As far as I can tell, stuff like procstat -ka doesn't run until it's already over, at which point there's nothing to see. Sorry I don't have more information about that. Unfortunately, we discussed the status of this today, and my update-to-NFSv4 project has basically been killed; we're backing off to NFSv3. Thanks for the help and information and all the hard work on NFS for many many years!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABXB=RRR_WVLxV-tUcSpu2jHm_AQXPAO-yfKDH64=T-bsHOXFQ>