Date: Sat, 10 Mar 2018 22:20:42 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: NAGY Andreas <Andreas.Nagy@frequentis.com>, "'freebsd-stable@freebsd.org'" <freebsd-stable@freebsd.org> Subject: =?iso-8859-1?Q?Re:_NFS_4.1_RECLAIM=5FCOMPLETE_FS=A0failed_error_in_combin?= =?iso-8859-1?Q?ation_with_ESXi_client?= Message-ID: <YQBPR0101MB1042AA8E2167F385AEEE5BFDDDDD0@YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <D890568E1D8DD044AA846C56245166780124AFD68A@vie196nt> References: <D890568E1D8DD044AA846C56245166780124AFD408@vie196nt> <YQBPR0101MB1042BE8D8A530CA8A905552FDDDD0@YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM>, <D890568E1D8DD044AA846C56245166780124AFD68A@vie196nt>
next in thread | previous in thread | raw e-mail | index | archive | help
NAGY Andreas wrote: >Thanks, the not issuing delegation warnings disappeared with this patch. > >But now there are some new warnings I haven't seen so far: >2018-03-10T13:01:39.441Z cpu8:68046)WARNING: NFS41: NFS41FSOpGetObject:214= 8: Failed to >get object 0x43910e71b386 [36 c6b10167 9b157f95 5aa100fb 8ffc= f2c1 c 2 9f22ad6d 0 0 0 0 0]: >Stale file handle I doubt these would be related to the patch. A stale FH means that the clie= nt tried to access a file via its FH after it was removed. (Normally this is a client b= ug, but hopefully not one that will cause grief.) >These only appear several times after a the NFS share is mounted or remoun= ted after a >connection loss. >Everything works fine, but haven't seen them till I applied the last patch= . > >andi Ok. Thanks for testing all of these patches. I will probably get cleaned up= versions of them committed in April. The main outstanding issue is the Readdir one about directory changing too = much. Hopefully I can find out something about it via email. Have fun with it, rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YQBPR0101MB1042AA8E2167F385AEEE5BFDDDDD0>