-
-
Notifications
You must be signed in to change notification settings - Fork 743
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
debug-info command #1122
Comments
|
note: some of these infos are already output if an exception happens. so, the first step would be to maybe add more useful stuff there and then reuse the same code for debug-info command (so one can get it even without an exception happening). |
implement borg debug-info, fixes #1122
|
Base implemented in #1481 |
|
yeah, that's a pretty good start. should we add more stuff in there? in the original post, i suggested two more metrics:
maybe it would be tricky to arbitrarily extract that without any context, especially if we're handling a backtrace. maybe an optional argument could be a repository that would give statistics about the repo? unless there's a good "stats" command already out there - from what I understand, borg info is still limited to operating on archives (and not repositories). |
|
Currently, the command is without parameter. As this adds new functionality (while #1481 just calls existing code via another means), I guess we keep just the basic version in 1.0-maint and extend its functionality in 1.1/master. |
|
Maybe we want to extend it a bit for 1.1. |
|
btw, do we really want this to be in the debug command? |
|
We also have borg-info repo since a while where more user-relevant stuff is found (key type, location, cache location, repo ID, size). |
|
current master branch output: (edited by enkore: updated) |
|
removed from milestone, can be done later also. |
|
Guess we just keep it as is for now. Adding stuff that can be done by |
writing up the #1107 bug report, i realized i went through a number of steps that seem intuitive to me, but that are not necessarily obvious to users. furthermore, I had to type down a bunch of commands by hand, which is annoying.
it would be nice if there was a borg-maintained single command that would wrap together a list of properties that are important to submit as part of a bug report. to quote #1107, what I used there is:
or, as a list:
lsb_release -b: operating system name, version and codename (Debian GNU/Linux 8.4 (jessie))uname -a: kernel version, architecture and build dates (Linux marcos 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-1 (2016-03-06) x86_64 GNU/Linux)borg --version: self-explanatoryborg list /media/sdc2/borg | wc -l: the number of archives in the repositorytime borg info /media/sdc2/borg/::marcos-2016-05-30: the size of the last archive, with some timing informationI realize that I forgot to mention the python version number, which should include the compiler version. I wonder if we don't want to extract certain parts of the environment as well.
it would also be great if
borg infowould operate without an archive name, to give information about a whole repository without having to guess the archive name.The text was updated successfully, but these errors were encountered: