Paths changed from /mnt/ to /mnt/rockstor

Troubleshooting
1

Hey everyone,

I understand that Rockstor ist quite Bleeding Edge, but isn’t changing the paths for your shares a bit drastic? I don’t know when this was introduced (I upgraded to 3.9 yesterday), but it completely destroyed my Seafile installation. It’s honestly a pain in the ass to change the path in several configuration files and I don’t see this change in the blog post regarding the 3.9 release. For everyone that doesn’t know what I mean: My shares (backup, seafile…) were located at /mnt2/ until yesterday, now all the folders for the shares are empty, I thought I lost all my files. But then I noticed the new rockstor folder and saw that my shares are now located in /mnt2/rockstor/.

I just wanted to let you know that it would be nice to announce such changes so that I don’t get a heart attack next time.

2

@der_eismann

Yes it would be.

I’m not aware of one actually !!

I fully agree with this and I like to think that we are quite good at announcing changes but there hasn’t been such a change!

I think what you are seeing is a problem with your install some how ie on pre-release code as of just now I have:

mount | grep btrfs
/dev/sda3 on / type btrfs (rw,relatime,space_cache,subvolid=258,subvol=/root)
/dev/sda3 on /home type btrfs (rw,relatime,space_cache,subvolid=257,subvol=/home)
/dev/mapper/luks-a47f4950-3296-4504-b9a4-2dc75681a6ad on /mnt2/luks-pool-on-native-name type btrfs (rw,relatime,ssd,space_cache,subvolid=5,subvol=/)
/dev/mapper/luks-3efb3830-fee1-4a9e-a5c6-ea456bfc269e on /mnt2/luks-pool-on-custom-name type btrfs (rw,relatime,ssd,space_cache,subvolid=5,subvol=/)
/dev/sda3 on /mnt2/rockstor_rockstor type btrfs (rw,relatime,space_cache,subvolid=5,subvol=/)
/dev/sda3 on /mnt2/home type btrfs (rw,relatime,space_cache,subvolid=257,subvol=/home)
/dev/sda3 on /mnt2/rock-ons-root type btrfs (rw,relatime,space_cache,subvolid=264,subvol=/rock-ons-root)
/dev/sda3 on /mnt2/root type btrfs (rw,relatime,space_cache,subvolid=258,subvol=/root)
/dev/sda3 on /mnt2/plex-config type btrfs (rw,relatime,space_cache,subvolid=265,subvol=/plex-config)
/dev/sda3 on /mnt2/plex-data type btrfs (rw,relatime,space_cache,subvolid=266,subvol=/plex-data)

Has anyone else seen such a mount point change such as this as it looks very much like something as gone wrong with @der_eismann’s mount arrangements: which is quite strange given they are automated?

3

Thanks for your fast reply. These are my mount entries:

/dev/sda4 on / type btrfs (rw,relatime,seclabel,space_cache,subvolid=257,subvol=/root)
/dev/sda4 on /home type btrfs (rw,relatime,seclabel,space_cache,subvolid=258,subvol=/home)
/dev/sda4 on /mnt2/rockstor type btrfs (rw,relatime,seclabel,space_cache,subvolid=5,subvol=/)
/dev/sda4 on /mnt2/backup type btrfs (rw,relatime,seclabel,space_cache,subvolid=263,subvol=/backup)

This is my pool:

tree /mnt2 -L 2
├── backup
│   ├── vm_backup
│   └── WindowsImageBackup
├── data
├── docker
├── home
├── rockstor
│   ├── backup
│   ├── data
│   ├── docker
│   ├── home
│   ├── root
│   └── seafile
├── root
└── seafile

And these are my shares:

So somehow all of them - except the backup share - got moved into the rockstor folder.