Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see:
viewtopic.php?t=158230
Linux Kernel, Network, and Services configuration.
shogun1234
Posts: 156 Joined: 2006-07-13 08:04
Has thanked: 3 times
#1
Post
by shogun1234 » 2022-11-22 20:13
I just found this backup tool a while ago. Am still learning how to use it. I attempt to create a snapshot with the command
Code: Select all
$ doas timeshift --create --comments "first" --tags D
But it throws error
Code: Select all
(process:11299): GLib-GIO-CRITICAL **: 21:08:54.036: g_file_get_path: assertion 'G_IS_FILE (file)' failed
** (process:11299): CRITICAL **: 21:08:54.036: tee_jee_file_system_path_combine: assertion 'path1 != NULL' failed
** (process:11299): CRITICAL **: 21:08:54.036: tee_jee_file_system_dir_exists: assertion 'dir_path != NULL' failed
Mounted '/dev/nvme0n1p2' at '/run/timeshift/11299/backup'
------------------------------------------------------------------------------
Estimating system size...
Creating new snapshot...(RSYNC)
Saving to device: /dev/nvme0n1p2, mounted at path: /run/timeshift/11299/backup
Syncing files with rsync...
E: rsync returned an error
E: Failed to create new snapshot
Failed to create snapshot
------------------------------------------------------------------------------
Removing snapshots (incomplete):
------------------------------------------------------------------------------
Removing '2022-11-22_21-08-54'...
Removed '2022-11-22_21-08-54'
------------------------------------------------------------------------------
Found stale mount for device '/dev/nvme0n1p2' at path '/run/timeshift/11299/backup'
Unmounted successfully
I have rsync installed
Code: Select all
$ rsync --version
rsync version 3.2.6 protocol version 31 ...
I don't find related answers to my problem. What could be the root cause? And how to fix it? Many thanks
sunrat
Administrator
Posts: 6494 Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 118 times
Been thanked: 476 times
#2
Post
by sunrat » 2022-11-22 23:45
I'd guess a path error. Don't think you should be attempting to write to /run/
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
shogun1234
Posts: 156 Joined: 2006-07-13 08:04
Has thanked: 3 times
#3
Post
by shogun1234 » 2022-11-23 23:23
sunrat wrote: ↑ 2022-11-22 23:45
I'd guess a path error. Don't think you should be attempting to write to /run/
Is there any place that I can specify the place from which to write? In the help doc's create option there is no way to specify that kind of info
Code: Select all
Backup:
--check Create snapshot if scheduled
--create Create snapshot (even if not scheduled)
--comments <string> Set snapshot description
--tags {O,B,H,D,W,M} Add tags to snapshot (default: O)
The only related place I find is in Examples section, but it's for restore operation.
Code: Select all
Examples:
...
timeshift --restore --snapshot '2014-10-12_16-29-08' --target /dev/sda1
...
Any way to specify that location? Or any doc that may have explanation about this? Thanks.
Region5_IHC
Posts: 8 Joined: 2022-12-24 10:59
Has thanked: 2 times
#4
Post
by Region5_IHC » 2023-02-03 21:08
Did you find an answer to this? I believe I have same error. If writing to
/run/ is the problem, I just need to mount it somewhere else? Also I didn't specify a mount point of
/run/ during install and creation of partitions so why is it mounted there?
I was able to write/manually create snapshots/write to that location yesterday so i don't understand.
Also wondering if its
$PATH related...?
GLib-GIO-CRITICAL site:forums.debian.net to search Google.
Linux noob respectfully seeking help/solution
Cron mailed this to me...
Code: Select all
Date: Fri, 03 Feb 2023 15:00:01 -0500
(process:263152): G Lib-GIO-CRITICAL **: 15:00:01.732: g_file_get_path: assertion 'G_IS_FILE (file)' failed
** (process:263152): CRITICAL **: 15:00:01.732: tee_jee_file_system_path_combine: assertion 'path1 != NULL' failed
** (process:263152): CRITICAL **: 15:00:01.732: tee_jee_file_system_dir_exists: assertion 'dir_path != NULL' failed
/dev/sda9 is mounted at: /run/timeshift/backup, options: rw,relatime
Daily snapshots are enabled
Last daily snapshot is 16 hours old
Region5_IHC
Posts: 8 Joined: 2022-12-24 10:59
Has thanked: 2 times
#6
Post
by Region5_IHC » 2023-02-22 15:56
I'm still receiving errors to my local inbox. I think I found the solution but not exactly sure how to navigate the Git page. I see issue is closed, and the fix is something to do with changing the PATH. Can someone please help me see where exactly on the Git page the link is for directions to fix.
Respectfully Requesting Help, Thanks
The link to what im almost positive the fix/solution is....
GLib-GIO-CRITICAL/teejee/timeshift
The errors i get to my inbox....
Code: Select all
To: root@debian
Subject: Cron <root@debian> timeshift --check --scripted
Date: Wed, 22 Feb 2023 10:00:01 -0500
(process:13970): GLib-GIO-CRITICAL **: 10:00:01.664: g_file_get_path: assertion 'G_IS_FILE (file)' failed
** (process:13970): CRITICAL **: 10:00:01.664: tee_jee_file_system_path_combine: assertion 'path1 != NULL' failed
** (process:13970): CRITICAL **: 10:00:01.664: tee_jee_file_system_dir_exists: assertion 'dir_path != NULL' failed
/dev/dm-4 is mounted at: /run/timeshift/backup, options: rw,relatime
Daily snapshots are enabled
Last daily snapshot is 10 hours old