public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>,
	Hannes Laimer <h.laimer@proxmox.com>
Subject: [pbs-devel] applied: [PATCH proxmox-backup] docs/technical-overview: add troubleshooting section
Date: Wed, 22 Sep 2021 07:47:00 +0200	[thread overview]
Message-ID: <b42a0189-6103-b3c3-296e-ab8847fa7eb9@proxmox.com> (raw)
In-Reply-To: <20210920091839.12252-1-h.laimer@proxmox.com>

On 20.09.21 11:18, Hannes Laimer wrote:
> ---
>  docs/technical-overview.rst | 58 +++++++++++++++++++++++++++++++++++++
>  1 file changed, 58 insertions(+)
> 
>

applied, thanks!

I reformated the text and adapted it also a bit wording/grammar wise, but it'd be great
if Dylan could take another look.

I also changed thew use of relative paths in the examples to absolute ones with some
meaning encoded, IMO that is easier for a non-involved user to understand what's going
on.

In the recovery example I tried to convey that skip-crc is also useful for trying to
restore partially corrupted files.
There it'd be still good to add a sentence to where the files will be restored too, as
those are rather big and thus it may be relevant to know and maybe even have an optional
param for that (if not already there?)

Also, while reading over this I though again that a `diff` command would be interesting,
i.e., one that allows to pass two snapshots and outputs the amount of differing chunks
(or even the full list + positions with a --verbose option). 




      reply	other threads:[~2021-09-22  5:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-20  9:18 [pbs-devel] " Hannes Laimer
2021-09-22  5:47 ` Thomas Lamprecht [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b42a0189-6103-b3c3-296e-ab8847fa7eb9@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=h.laimer@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal