File names not displaying on S3 mounts

[melmatsuoka]

I'm having an issue with file names not showing up on S3 mounts, using Mountain Duck 4.16.3 on macOS 14.6.1. The folder names all show up fine, but all the files within the folder don't show up.

The file names on the same S3 share, using the same S3 credentials, show up fine in Cyberduck, however.

[dkocher]

The obvious reason would be the filename matching the following regular expression which by defaults filters filenames in Mountain Duck.

fs.filenames.filter.name.regexp=[\\.]{1,2} .*[\\/\\\\].* \\.file-segments

However your screenshot does not indicate a match. Can you enable debug logging and search the log file for lines containing FilesystemListFilter.

[dkocher]

The log shows the files are filtered because of the applied storage class. The default in Mountain Duck is to skip all files in Glacier or Deep Archive storage classes, as these files cannot be retrieved without restoring first.

The default setting is

fs.filenames.filter.storageclass.regexp=GLACIER DEEP_ARCHIVE

[melmatsuoka]

hmm..apologies. Had to reupload the log file.

mountainduck.log

[melmatsuoka]

The log shows the files are filtered because of the applied storage class. The default in Mountain Duck is to skip all files in Glacier or Deep Archive storage classes, as these files cannot be retrieved without restoring first.

The default setting is

fs.filenames.filter.storageclass.regexp=GLACIER DEEP_ARCHIVE

Ah, that's interesting. So you can't retrieve just the filenames of objects in Glacier/GDA without restoring them first? I dont have any issues with Cyberduck being able to do this with the default settings on the same S3 bucket(s)?

[dkocher]

Retrieving the keys (filenames) is not a problem but In Mountain Duck mounting as a filesystem it is very common that some application will attempt to read the file contents (for example to render a preview in Finder.app or Windows Explorer). Because that will fail for archived files we choose to not display them by default.

[melmatsuoka]

Ok that makes sense. Is there no practical workaround for this, at least on macOS?

I'm using NeoFinder to index the files/folders in my cloud archives (one of the new features recently added to NeoFinder was direct support for indexing Mountain Duck mounted cloud volumes). I'm hoping there might be some way in situations like this to just display the names of the files (and any associated metadata such as file size, mod/create dates etc) without allowing system processes to actually read the contents of the files themselves if they specifically belong to the S3 Glacier/GDA storage class ?