delete

[ghost]

I am a bookaholic. If you are a decent person, you will not sell me another book.

[hasse69]

Sorry for late response, for obvious reasons things have been a bit upside down lately.

The reason I am creating an issue is because I couldn't find documentation explaining this.

The simple answer is that there is no such documentation because there is no such feature. The file exclusion that you get from the --exclude option is more about what contents outside of RAR files that should not be searched for inside it either. Normally that can be file browser specific file etc.

The mount you do when using rar2fs is very close to a simple bind mount. It replicates the source file system completely with the addition of expanding files inside RAR archives. Having filters to hide things on the source file system level would work against the intended design of rar2fs, But then you are also not 100% clear about what you wish to filter? Is it things outside of RAR files or the RAR files themselves? In the latter case I must ask what is the use case for wanting to do that? If you wish to have filtering on top of rar2fs I would search for some other FUSE file system that has that as its primary objective. Stacking FUSE file systems on top of each other is a very common approach to gain multiple extension to the standard source file system.

[hasse69]

Unless there is something more you wish to add I would like to close this issue soon.

[hasse69]

Again. I fail to see the issue here, sorry.

I wouldn't want to decompress the subtitles.

If you do not wish to extract the file then don't? In what way would a filter help here? You extract what you chose to extract, nothing else. There is no extraction going on unless you actually try to read data from a file. The folder lookup (collecting RAR header meta data) is something else and also performed only once and any subsequent queries are picked from the cache.

The problem for use-cases involving e.g. rclone etc is of course that any access of files will have to be performed across a potentially slow network. But nevertheless, rar2fs would not try to download the complete file if only the header is needed, which is the case for populating a directory. But for volumes you need to be careful and make sure to use the --seek-length option or you might end up downloading hundreds of files when only one was in fact needed. But again, to populate a directory only requires a small part of the entire file (the header) to be downloaded. If for some reason the entire file is downloaded then that is a limitation of rclone rather than rar2fs?

[hasse69]

AFAIK the files you are referring to usually comes in two level archives (RAR in RAR). For that to even work you need to stack rar2fs filesystems since only one level is supported for each mount.

[hasse69]

I will close this issue now since I do not think there is much more to add.