Bug#898165: Regression in [v2] nfs: Fix ugly referral attributes ?

2018-05-17 Thread Chuck Lever
ydata.com> CommitDate: Thu Apr 23 14:43:54 2015 -0400 nfs: Fetch MOUNTED_ON_FILEID when updating an inode > Best regards, > Moritz > > On 05.11.2017 21:45, Chuck Lever wrote: >> Before traversing a referral and performing a mount, the mounted-on >> directory looks s

Bug#898165: Regression in [v2] nfs: Fix ugly referral attributes ?

2018-05-18 Thread Chuck Lever
> On May 17, 2018, at 5:48 PM, Moritz Schlarb <schla...@uni-mainz.de> wrote: > > Hi Chuck, > > On 17.05.2018 16:15, Chuck Lever wrote: > >> Just a shot in the dark: Wondering if v3.16 needs >> >> commit ea96d1ecbe4fcb1df487d99309d3157b4ff5fc02

Bug#940821: NFS Caching broken in 4.19.37

2021-02-20 Thread Chuck Lever
0% reproducible with any kernel from 4.9 to 5.4, stable or backports. It > may exist in earlier versions, but I do not have a machine with anything > before 4.9 to test at present. Confirming you are varying client-side kernels. Should the Linux NFS client maintainers be Cc'd? > From 1-2 make clean && make cycles to one afternoon depending on the number > of machine cores. More cores/threads the faster it does it. > > I tried playing with protocol minor versions, caching options, etc - it is > still reproducible for any nfs4 settings as long as there is client side > caching of metadata. > > A. > >> >> Regards, >> Salvatore >> > > -- > Anton R. Ivanov > Cambridgegreys Limited. Registered in England. Company Number 10273661 > https://www.cambridgegreys.com/ -- Chuck Lever

Bug#579397: STAT_FAIL to debian for SM_MON of 192.168.120.254, No canonical hostname found for 192.168.120.254

2010-05-24 Thread Chuck Lever
On 05/21/10 09:38 PM, Ben Hutchings wrote: On Sat, 2010-05-22 at 07:49 +0800, Steven Shiau wrote: Same problem here. However, mine is on the client side. On sid system, running kernel is 2.6.32-5-686, nfs-common is 1:1.2.2-1. When I mount my NFS server 192.168.120.254, it works. However, if I

Bug#579397: STAT_FAIL to debian for SM_MON of 192.168.120.254, No canonical hostname found for 192.168.120.254

2010-06-03 Thread Chuck Lever
On 05/24/10 11:22 AM, Chuck Lever wrote: On 05/21/10 09:38 PM, Ben Hutchings wrote: On Sat, 2010-05-22 at 07:49 +0800, Steven Shiau wrote: Same problem here. However, mine is on the client side. On sid system, running kernel is 2.6.32-5-686, nfs-common is 1:1.2.2-1. When I mount my NFS server

Bug#579397: STAT_FAIL to debian for SM_MON of 192.168.120.254, No canonical hostname found for 192.168.120.254

2010-07-06 Thread Chuck Lever
On 06/ 9/10 10:41 AM, Steven Shiau wrote: On 2010年06月06日 04:29, Ben Hutchings wrote: On Thu, 2010-06-03 at 17:08 -0400, Chuck Lever wrote: On 05/24/10 11:22 AM, Chuck Lever wrote: [...] We can probably remove the reverse mapping constraint for presentation addresses. A simple fix might

Bug#579397: STAT_FAIL to debian for SM_MON of 192.168.120.254, No canonical hostname found for 192.168.120.254

2010-08-08 Thread Chuck Lever
On Aug 8, 2010, at 12:59 AM, Ben Hutchings wrote: On Tue, 2010-07-06 at 13:05 -0400, Chuck Lever wrote: On 06/ 9/10 10:41 AM, Steven Shiau wrote: On 2010年06月06日 04:29, Ben Hutchings wrote: On Thu, 2010-06-03 at 17:08 -0400, Chuck Lever wrote: On 05/24/10 11:22 AM, Chuck Lever wrote

Bug#1067829: Fails to build on arm{el,hf} with 64bit time_t: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘time_t’ {aka ‘long long int’} [-We

2024-04-06 Thread Chuck Lever III
r > to properly credit the patch origin. > > Let me know if that works. I changed it slightly and only casting to > long long, and made it almost checkpatch clean. I suppose strftime(3) might be nicer, but this works. Reviewed-by: Chuck Lever mailto:chuck.le...@oracle.com>>