Re: [pure-ftpd] Sorry, we were unable to read [.]

Hi,

Am 24.02.2020 um 11:32 schrieb Lorenzo Milesi:

>> In your other mail you've already found out that it's the number of files
>> in the directory. This is an effect you see with many file systems when
>> the number of files in a directory exceeds a limit (often somewhere in the
>> range of 50,000 to 100,000).
> 
> Yes, but the OS doesn't seem to have any problem with that directory.

How exactly did you test that? By just doing an "ls -l" might not
show the effect. I'm not an expert of the details of every file
system out there but there are attributes of a file that are part
of the directory-entries themselves and "extended attributes" that
need to be accessed separately and are done on a per-file-basis. If you
don't access any of the "extended" attributes everything looks normal
but ends in a SHF-situation otherwise.

> I meant how can I debug the problem on the FTP server side, because it looks
> to me it's a matter of that. Unfortunately even after enabling Verbose mode
> I see no error, so I don't know how to work it out.

You can try stracing the pure-ftp-process. That should show you the file
system accesses the process is doing.


Cheers, Lothar