MX 21/3 error with MX Snapshot

[rod178]

/var/log/mx-snapshot.log

What you have posted is not the contents of the mx-snapshot.log
Attach the log, as mine attached

Note that the latest MX21.3 Update seems to have rectified the issue with Snapshot generation

[Fornhamfred]

mx-snapshot.log

[fehlix]

mx-snapshot.log

Maybe takeout the space from the snapshot path:
E.g change:

Code: Select all

/media/Backups/MX Snapshots/snapshot/

to something like

Code: Select all

/media/Backups/MX-Snapshots/snapshot/

or

Code: Select all

/media/Backups/MX_Snapshots/snapshot/

at least until space handling in path is properly fixed.
Note: having spaces in path's is known to call for trouble.
HTH

[Fornhamfred]

mx-snapshot.log

Maybe takeout the space from the snapshot path:
E.g change:

Code: Select all

/media/Backups/MX Snapshots/snapshot/

to something like

Code: Select all

/media/Backups/MX-Snapshots/snapshot/

or

Code: Select all

/media/Backups/MX_Snapshots/snapshot/

at least until space handling in path is properly fixed.
Note: having spaces in path's is known to call for trouble.
HTH

Thanks Fehlix
That has sorted the problem.

[thebookkeeper]

Real Linux users don't use spaces in file and path information anyway. These spaces are an annoying Windows habit among young switchers. This is not a program error, but a user error!

[Adrian]

Well, it's better if the program doesn't stumble on that, I will see what I can do about that.

[Adrian]

The latest version should fix the blank space in folder/file name issue.

[artytux]

I purposely put blank spaces in folder names and got no problems or errors.
Did notice MX Snapshot is running with less cpu use and of course temperature was down also,
I don't think Ive added much to my install in the previous week or two seems the snapshot are bit bigger now ( not a problem have dedicated 16GB usbstick) they were just under 4GB now just over 6GB.
In the event of hardware failure good to have MX Snapshot certainly will not be install failure, rock solid distro.
Posted to say Thank You to Adrian.

[Adrian]

I don't think Ive added much to my install in the previous week or two seems the snapshot are bit bigger now

Check the compression algorithm that's selected when you take the snapshot. It might have switched to LZ4 default one from whatever you had selected. LZ4 is a good selection if you don't care about space, if you do use Zstd.

[artytux]

I don't care much about MB/GB sizes, memory is cheap enough to buy, sure there must a joke in there somewhere, can't remember, anyway with new (for me) software I usually select the middle option, best compromise, checked setting was set on and still is on Zstd, I'll keep watch see what happens, like I stated it's not an issue.