Closed Nischi85 closed 3 years ago
I believe something similar has been asked about before in issue #134
If you read the man page for rar2fs (https://github.com/hasse69/rar2fs/wiki/Manual-Page) I think you will find that the --exclude
option (perhaps not the best name) has nothing to do really with filtering existing contents from your source folder or mount point. It is more about ignoring things that is verified not to be present to avoid some overhead.
Currently there is no way to filter out files or directories in the way that you explain here.
But as I have already mentioned in the issue above, what exactly is the use case for needing such a feature?
Whatever you point to that looks beneath the mount point should be able to handle that for you?
EDIT: A quick search game me this https://github.com/gburca/rofs-filtered Unless you need write access to to your mount point this seems like a perfect fit for your use-case?
Thank you hasse69. tried searching for an answer, but I guess my google-skills wheren't up to the task.
My use case is that I have a lot of uneeded files for my Emby-collection, and just wanted to "filter" them out.
Looks like that rofs-filtered will do the trick, thank you again!
If you stack rofs-filtered on top of a rar2fs mount it is only the rofs-filtered mount point that will become read-only. If you mounted read/write using rar2fs its mount point will remain writable. Then how that will affect the rofs-filtered caches (if any) etc I cannot answer.
Closing.
Questions below are for outside of rar-archives.
Is there some way to exclude with wildcard folders ? ex --exclude=//Sample/ Is there some way to exclude with wildcard for files? ex. --exclude=sample.*
I've tried various variations withouch success.