-
-
Notifications
You must be signed in to change notification settings - Fork 740
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
borg mount
does not show return code
#8308
Comments
If you don't use the Guess we could implement supporting this (for consistency), but it wouldn't be very useful. If you use |
BTW, 1.2.0 is relatively old. If you run debian or ubuntu, try backports or the ppa. |
I upgraded to borg 1.4.0 from the ppa now. The following output is all from borg 1.4.0
I don't see why it should not be useful. I run borg in a script and would like to see all the returncodes in text to see whether everything worked as expected. And at least for consitency it should be implemented (in my opinion).
I tried that. However the command seems to hang somewhere. It does mount the repo but the command does not finish. $ borg mount :: backup_restore/ --show-rc --foreground
^C^C/usr/lib/python3/dist-packages/trio/_core/_run.py:2235: RuntimeWarning: Trio guest run got abandoned without properly finishing... weird stuff might happen
terminating with success status, rc 0 See the Here the output with a $ borg mount :: backup_restore/ --show-rc --foreground --debug
using builtin fallback logging configuration
33 self tests completed in 0.20 seconds
SSH command line: ['ssh', 'xxx@yyy', 'borg', 'serve', '--debug']
Remote: using builtin fallback logging configuration
Remote: 33 self tests completed in 0.16 seconds
Remote: using builtin fallback logging configuration
Remote: Initialized logging system for JSON-based protocol
Remote: Resolving repository path b'xxx'
Remote: Resolved repository path to 'xxx'
Remote: Verified integrity of xxx/index.940
TAM-verified manifest
security: read previous location 'xxx'
security: read manifest timestamp '2024-07-28T01:09:39.019014'
security: determined newest manifest timestamp as 2024-07-28T01:09:39.019014
security: repository checks ok, allowing access
mount data cache capacity: 4 chunks
Mounting filesystem
Initializing pyfuse3
Calling fuse_session_new
Calling fuse_session_mount
pyfuse-02: No tasks waiting, starting another worker (now 2 total).
^C^C/usr/lib/python3/dist-packages/trio/_core/_run.py:2235: RuntimeWarning: Trio guest run got abandoned without properly finishing... weird stuff might happen
Calling fuse_session_destroy
RepositoryCache: current items 0, size 0 B / 2.15 GB, 0 hits, 0 misses, 0 slow misses (+0.0s), 0 evictions, 0 ENOSPC hit
RemoteRepository: 236 B bytes sent, 3.27 kB bytes received, 5 messages sent
terminating with success status, rc 0 It says |
It doesn't "hang", it is just quite silent if you don't use The process ends if you:
What I meant by "not that interesting" without
BTW, read and follow the upgrade notes when upgrading from 1.2.0 to 1.4.0, esp. the CVE related upgrade instructions at the top of the changelog. |
That makes sense^^. So back to the original issue: I'd find a
Thank you. Done! |
Is this a BUG / ISSUE report or a QUESTION?
BUG
System information. For client/server mode post info for both machines.
Your borg version (borg -V).
borg 1.2.0
Full borg commandline that lead to the problem (leave away excludes and passwords)
BORG_PASSPHRASE=XXX borg mount --show-rc ::2024-07-28T03-00-01 /mnt/backup_restore
Describe the problem you're observing.
borg mount
does not show the return code if asked to.There seems to be something wrong with the printing. Normally there should be an empty line before the new command prompt. Should look like this:
Running any other commands shows the rc
or
or
The text was updated successfully, but these errors were encountered: