I’ve been playing with different automated ways of performing send/receive to allow for a more resilient backup setup and during this I noticed that in one of my shares I have what appears to be some orphaned directories that were created by the Scheduled task jobs I had created to perform snapshots on the shares.
So for example, I have the following:
[root@rockstor ]# tree -L 2 -a /mnt2/Docker-Persistent-Storage/
/mnt2/Docker-Persistent-Storage/
├── .Docker-Persistent-Storage-Backup_201809260200
├── .Docker-Persistent-Storage-Backup_20180927
├── .Docker-Persistent-Storage-Backup_201809280300
├── .Docker-Persistent-Storage-Backup_201809290300
├── .Docker-Persistent-Storage-Backup_201809300300
├── ombi
│ └── config
├── portainer
│ ├── compose
│ ├── config.json
│ ├── data
│ ├── portainer.db
│ ├── portainer.key
│ ├── portainer.pub
│ └── tls
The ‘.Docker-Persistent-Storage-Backup*’ directories were created as part of a scheduled task config’ed via the GUI. During my testing I had decided to remove the scheduled task and also to delete the relevant snapshots listed in the Shares > Snapshots for the aforementioned Share. Also reviewed the overall ‘Snapshots’ page in the GUI to ensure no other snapshots existed.
They all were removed fine from the UI but when navigating around in the CLI they still appear. They are not sub volumes (btrfs sub del doesn’t work) and a simple rm -rf also doesn’t work (says “operation not permitted” even as root user). They dont appear to be impacting anything but my OCD certainly finds them troublesome. Also, I’d just like to understand why they cant be simply removed…
Thanks for any input.