TrueCloudLab/restic
16
0
Fork 2
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

Fix typos

Browse source
This commit is contained in:
Martin Michlmayr 2023-10-26 14:27:19 +08:00 committed by Michael Eischer
parent de6135351e
commit 0b6ccea461
4 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/030_preparing_a_new_repo.rst
View file

@ -331,7 +331,7 @@ Wasabi
************ ************
`Wasabi <https://wasabi.com>`__ is a low cost Amazon S3 conformant object storage provider. `Wasabi <https://wasabi.com>`__ is a low cost Amazon S3 conformant object storage provider.
Due to it's S3 conformance, Wasabi can be used as a storage provider for a restic repository. Due to its S3 conformance, Wasabi can be used as a storage provider for a restic repository.
- Create a Wasabi bucket using the `Wasabi Console <https://console.wasabisys.com>`__. - Create a Wasabi bucket using the `Wasabi Console <https://console.wasabisys.com>`__.
- Determine the correct Wasabi service URL for your bucket `here <https://wasabi-support.zendesk.com/hc/en-us/articles/360015106031-What-are-the-service-URLs-for-Wasabi-s-different-regions->`__. - Determine the correct Wasabi service URL for your bucket `here <https://wasabi-support.zendesk.com/hc/en-us/articles/360015106031-What-are-the-service-URLs-for-Wasabi-s-different-regions->`__.
@ -822,7 +822,7 @@ To make this work we can employ the help of the ``setgid`` permission bit
available on Linux and most other Unix systems. This permission bit makes available on Linux and most other Unix systems. This permission bit makes
newly created directories inherit both the group owner (gid) and setgid bit newly created directories inherit both the group owner (gid) and setgid bit
from the parent directory. Setting this bit requires root but since it from the parent directory. Setting this bit requires root but since it
propagates down to any new directories we only have to do this priviledged propagates down to any new directories we only have to do this privileged
setup once: setup once:
.. code-block:: console .. code-block:: console

2
doc/040_backup.rst
View file

@ -146,7 +146,7 @@ change detection rule based on file metadata to determine whether a file is
likely unchanged since a previous backup. If it is, the file is not scanned likely unchanged since a previous backup. If it is, the file is not scanned
again. again.
The previous backup snapshot, called "parent" snaphot in restic terminology, The previous backup snapshot, called "parent" snapshot in restic terminology,
is determined as follows. By default restic groups snapshots by hostname and is determined as follows. By default restic groups snapshots by hostname and
backup paths, and then selects the latest snapshot in the group that matches backup paths, and then selects the latest snapshot in the group that matches
the current backup. You can change the selection criteria using the the current backup. You can change the selection criteria using the

2
doc/045_working_with_repos.rst
View file

@ -337,7 +337,7 @@ over 5 separate invocations:
$ restic -r /srv/restic-repo check --read-data-subset=4/5 $ restic -r /srv/restic-repo check --read-data-subset=4/5
$ restic -r /srv/restic-repo check --read-data-subset=5/5 $ restic -r /srv/restic-repo check --read-data-subset=5/5
Use ``--read-data-subset=x%`` to check a randomly choosen subset of the Use ``--read-data-subset=x%`` to check a randomly chosen subset of the
repository pack files. It takes one parameter, ``x``, the percentage of repository pack files. It takes one parameter, ``x``, the percentage of
pack files to check as an integer or floating point number. This will not pack files to check as an integer or floating point number. This will not
guarantee to cover all available pack files after sufficient runs, but it is guarantee to cover all available pack files after sufficient runs, but it is

2
internal/fuse/file.go
View file

@ -143,7 +143,7 @@ func (f *openFile) Read(ctx context.Context, req *fuse.ReadRequest, resp *fuse.R
// the methods being called are responsible for appropriate synchronization. // the methods being called are responsible for appropriate synchronization.
// //
// However, no lock needed here as getBlobAt can be called conurrently // However, no lock needed here as getBlobAt can be called conurrently
// (blobCache has it's own locking) // (blobCache has its own locking)
for i := startContent; remainingBytes > 0 && i < len(f.cumsize)-1; i++ { for i := startContent; remainingBytes > 0 && i < len(f.cumsize)-1; i++ {
blob, err := f.getBlobAt(ctx, i) blob, err := f.getBlobAt(ctx, i)
if err != nil { if err != nil {