pigmonkey / cryptshot Goto Github PK

When the LUKS volume is already mounted,
for instance, when I mount it to check what is is effectively backup (I am in test mode) ;
then the script does not go away, stopping with "error 5" at "cryptsetup luksOpen" command.
(I added "set -x" at the beginning of the script to see what appends)

Should it be possible and safe to let the script continue with an alweady mapped volume and mount it at the $MOUNTPOINT ?
I alwready checked that, after luksOpen, I can mount and look inside the volume in user mode (typically in /media/myuser/UUID) and still having it open with the "cryptsetup luksOpen" command from the script, in root mode.

Is there some side effets that could create ?
The side effect that could now appends is that, when looking in the backups in user mode, and if it is time to make a new backup, it fails.

I think of using (your?) backitup script to sheddule cryptshot (and rsnapshot) but to error of letting the backup directory opened in user space is easy to do, and backups need to be donne !

Other ideas, workarounds or real solutions ?

Excuse my english, my real langage is french ;-)

I want to use your script, thanks for having doing it ;-)

I want to make backups on a usb-drive, and a meeted a difficulty when connecting it to another usb-port.

I founded a solution by changing all "uuid" references in the script by "partuuid" witch , in my knowledge, will never change.

I also change [ echo "Volume $PARTUUID not found." ] by [ echo "$volume not found." ] for a outputa bit more explicit>

Are you ok with that and do you want to enhance the script with it ?

Another bug-report for another topic to follow ...

To make the script more robust, verify that the BACKUP program is existing and executable, otherwise cryptshot will fail and leaves you with an unencrypted and mounted filesystem.