Re: [lustre-discuss] ls command blocked in some dir

2020-09-23 Thread 肖正刚
Hi, I disabled auto_scrub on all OSS use "lctl set_param osd-ldiskfs.*.auto_scrub=0"; then trace file command on client , nothing new returned and oss&mds&client can not see any messages newer. Franke, Knut 于2020年9月23日周三 下午11:59写道: > Hi, > > we've had a similar issue, though in our case there w

Re: [lustre-discuss] ls command blocked in some dir

2020-09-23 Thread Franke, Knut
Hi, we've had a similar issue, though in our case there were "FID-in-LMA [...] does not match the object self-fid" errors in the OSS logs. See LU-13392 for details. You could try disabling auto_scrub (lctl set_param osd_ldiskfs.*.auto_scrub=0) and check whether this causes lstat() to return somet

[lustre-discuss] ls command blocked in some dir

2020-09-23 Thread 肖正刚
Hi, all In one of our lustre filesystems,we found that 1) ls command blocked in some dir but ls --color=never worked. 2) some files can not be accessed, like cat/head/vim/file(i use strace to trace command "strace file .xxx" , stucked in lstat). " fstat(1, {st_mode