Json-CRITICAL error in update, timeshift is bugging?

filo · 20 May 2021 07:22

I found this one wihch cold be interesting for you to read and try to solve the timeshift problem:

github.com/teejee2008/timeshift

Json files describing the snapshots messed up

opened 03:25PM - 21 Sep 18 UTC

I am using Arch Linux together with BTRFS. For managing the snapshots I use time…shift. Today, after going back to earlier snapshots twice. But after the second time I noticed, that none of the snapshots was visible anymore. Starting timeshift via cli showed me following error messages: ` ~  sudo timeshift --list  1 /dev/sdb3 is mounted at: /mnt/timeshift/backup, options: rw,relatime,ssd,discard,space_cache,subvolid=5,subvol=/ E: JSON data must be UTF-8 encoded (process:6401): Json-CRITICAL **: 17:09:56.586: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed E: JSON data must be UTF-8 encoded (process:6401): Json-CRITICAL **: 17:09:56.586: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed E: JSON data must be UTF-8 encoded (process:6401): Json-CRITICAL **: 17:09:56.587: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed E: JSON data must be UTF-8 encoded (process:6401): Json-CRITICAL **: 17:09:56.587: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed E: JSON data must be UTF-8 encoded (process:6401): Json-CRITICAL **: 17:09:56.588: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed E: JSON data must be UTF-8 encoded (process:6401): Json-CRITICAL **: 17:09:56.588: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed E: JSON data must be UTF-8 encoded (process:6401): Json-CRITICAL **: 17:09:56.589: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed E: JSON data must be UTF-8 encoded (process:6401): Json-CRITICAL **: 17:09:56.589: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed E: JSON data must be UTF-8 encoded (process:6401): Json-CRITICAL **: 17:09:56.590: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed E: JSON data must be UTF-8 encoded (process:6401): Json-CRITICAL **: 17:09:56.590: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed Device : /dev/sdb3 UUID : f188b276-72df-4961-b99c-0aadd0268997 Path : /mnt/timeshift/backup Mode : BTRFS Device is OK 1 snapshots, 659.9 GB free Num Name Tags Description ------------------------------------------------------------------------------ 0 > 2018-09-21_17-00-01 D ` The last one was a snapshot immediately created after logging back in after reverting to an earlier snapshot. On further investigation I found out, that all the json files in /mnt/timeshift/backup/timeshift-btrfs/snapshots/ don't contain any data: ![image](https://user-images.githubusercontent.com/3685646/45890350-139b0900-bdc3-11e8-99b0-bab989edbde1.png) Is this a known issue? Can I use the old, still present snapshots with "fake" metadata json files in order to use them?

In my system I also see my snapshots in:
/run/timeshift/backup/timeshift-btrfs/snapshots