Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 17 Jan 2021 14:49:09 +0000
From:      Rick Macklem <rmacklem@uoguelph.ca>
To:        J David <j.david.lists@gmail.com>
Cc:        Konstantin Belousov <kostikbel@gmail.com>, "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org>
Subject:   Re: Major issues with nfsv4
Message-ID:  <YQXPR0101MB096854F3CB5423CB485BEDB1DDA50@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM>
In-Reply-To: <CABXB=RT08WUVy6dqcDwE9BDER4P79_h6zbTjsjoTV%2BrT4WiNBg@mail.gmail.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>

next in thread | previous in thread | raw e-mail | index | archive | help
 J David wrote:=0A=
>On Sat, Jan 16, 2021 at 5:57 PM Rick Macklem <rmacklem@uoguelph.ca> wrote:=
=0A=
>> Opens can be closed until all FreeBSD open file descriptors for the file=
=0A=
>> are closed.=0A=
>> --> Just the way it is. It is not an unintended leak. They go away once=
=0A=
>>       all file descriptors get closed,=0A=
>[...]=0A=
>> However, none of the above seems unexpected, except maybe for why=0A=
>> "ls" in the chroot opens 3 regular files each time. I don't know what=0A=
>> chroot actually does for something like "ls"? I'll look.=0A=
>=0A=
>It probably isn't anything ls is doing.  It's probably just the open=0A=
>of whatever shared libraries ls has in common with the shell running=0A=
>in the other window.=0A=
>=0A=
>And so, on a long-running system with frequently-accessed binaries (or=0A=
>just shared libraries) mounted over NFS, where it's unlikely that all=0A=
>descriptors will ever be closed at the same time, a hang/crash/failure=0A=
>essentially becomes inevitable?=0A=
Yes. If you have NFSv4 mounted shared libraries and an environment=0A=
where there is at least one process running using a given shared library=0A=
on the mount at any time, the NFSv4 Opens will accumulate and=0A=
eventually constipate the mount.=0A=
=0A=
>Is this a solvable problem?  (Outside of oneopenown.)=0A=
For this case, "oneopenown" is your only option.=0A=
=0A=
I think there might have been a nullfs/NFSv4 interaction issue,=0A=
but it appears to be resolved in FreeBSD13.=0A=
=0A=
rick=0A=
=0A=
Thanks!=0A=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YQXPR0101MB096854F3CB5423CB485BEDB1DDA50>