New User - Big Mistake?

Support
1

New user here. Hi.

Installed Stash in Container Station on QNAP NAS. Mapped directories to existing shared locations (all my containers have /config/[appname] directories for running configs in a separate location) and also mapped location to data directory where my curated library is located.

Pointed Stash at the directory and (from documentation) assumed it would scan the files to populate the database but leave the existing directory structure intact. On running the scan, it’s emptied the data directory (some 40TBs) and tried to copy them all into the /config location.

Unfortunately, now neither of the LUNs in functional - one is empty and the other is full due to the massive Stash database.

Is there a way to revert the scan actions and restore the file structue to it’s previous state and NOT have stash move the contents but only reference that data directory for content? (Stash config/blobs/metadata directories are all mapped from the docker host under /config/stash/[dir]

Thanks!

2

Stash doesn’t move library files around. The only thing that stash does during startup that modifies the filesystem is clears the downloads and tmp subdirectories in the generated directory. During scanning, stash does not move any referenced library files and only creates files in the blobs and generated directories. The only thing that could move library files around during the scan process would be a plugin.

3

Pointed Stash at the directory and (from documentation) assumed it would scan the files to populate the database but leave the existing directory structure intact. On running the scan, it’s emptied the data directory (some 40TBs) and tried to copy them all into the /config location.

Post your docker compose showing how you mapped these volumes :thinking: