NSFS | List Objects | Make List Objects More Robust and Additionl Gaps

[shirady]

Environment info

• NooBaa Version: 5.19.0
• Platform: NC

Actual behavior

1. Currently (master) if an entry had EACCES on stat this entry is ignored. In other words, the list would not contain this key (as added in PR NC | Multi Protocol Access | List object with conflicting ownership #8751).
2. Currently, if an entry had ELOOP or ENAMETOOLONG on stat this entry is ignored. In other words, the list would not contain this key.
3. After PR NSFS | Fix Bug | Race Between List Object and Delete Object #8809 will be merged, that stat is called in a serial way.

More general

4. After PR NSFS | Fix Bug | Race Between List Object and Delete Object #8809 will be merged, we might look at all the cases where we used stat and think if we want to change the call to stat_if_exists.
5. Handling EPREM when extended attributes feature is not supported in the FS.

Expected behavior and suggestion (the numbers are adjusted to the title before)

1. We might want to add this key in the list. Therefore, we will need to change the stat that we use, currently in fs_napi we use the open system call inside for the extended attributes, but we may consider changing it so we can stat without open, we can also consider changing the context so the list objects will be by root.
2. We need to discuss if we want to ignore those errors as they can appear in FS cross protocol.
3. We need to think if we can somehow make the calls concurrent.

Steps to reproduce

1. list object in NSFS.

More information - Screenshots / Logs / Other output

none