<refsect1 id='description'>
<title>DESCRIPTION</title>
- <para>Create a snapshot at every login of a user, thus they always have a save
+ <para>Create a snapshot at every login of a user, thus they always have a safe
starting point.</para>
<para>As many users do not logout for some time, it is a good idea to
<term><option>send-compressed-data</option></term>
<listitem>
<para>Per default snbk will add the option --compressed-data iff
- supported by the source and target system. This can be disable by
+ supported by the source and target system. This can be disabled by
setting this value to false.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>QGROUP=<replaceable>qgroup</replaceable></option></term>
<listitem>
- <para>The btrfs quota group used for space aware cleanup
+ <para>The btrfs quota group used for space-aware cleanup
algorithms.</para>
<para>Only supported for btrfs.</para>
</listitem>
<varlistentry>
<term><option>COMPRESSION=<replaceable>algorithm</replaceable></option></term>
<listitem>
- <para>Defines the compression algorithm used for saving file
+ <para>Defines the compression algorithm used for saving the file
list. Allowed values are "none" and
"gzip". Depending on the installed libraries, some
compression algorithms might not be available.</para>
<para>The number and timeline cleanup algorithms can also try to
keep the space used by snapshots below a limit and the free space of
the filesystem above a limit. For the first condition quota must be
- setup, see command setup-quota. Additional the NUMBER_LIMIT and
+ setup, see command setup-quota. Additionally the NUMBER_LIMIT and
TIMELINE_LIMIT variables in the config file must have ranges (min- and
max-value). The algorithms will then make two passes:</para>
<para>The limit for the free space can be configured via the
FREE_LIMIT variable.</para>
- <para>Note: Since the cleanup is performed asynchronous from
+ <para>Note: Since the cleanup is performed asynchronously from
creating snapshots the observed snapshots can differ from the
expected snapshots according to the limits. Also btrfs stale
qgroups can exist temporarily.</para>
<listitem>
<para>Disable display of used space.</para>
<para>Calculating the used space needs some time. Thus
- this option can speedup the listing.</para>
+ this option can speed up the listing.</para>
</listitem>
</varlistentry>
<varlistentry>
</listitem>
<listitem>
<para>A "<computeroutput>p</computeroutput>" means the permissions
- are have changed.</para>
+ have changed.</para>
</listitem>
<listitem>
<para>An "<computeroutput>u</computeroutput>" means the user
<varlistentry>
<term><option>set-read-only-post <replaceable>subvolume</replaceable> <replaceable>fstype</replaceable> <replaceable>snapshot-number</replaceable></option></term>
<listitem>
- <para>Executed after a snapshot is set read-only or read-write</para>
+ <para>Executed after a snapshot is set read-only or read-write</para>
</listitem>
</varlistentry>
<varlistentry>
<refsect1 id='notes'>
<title>NOTES</title>
<para>There is no mechanism to ensure consistency of the files while a
- snapshot it made. E.g. the files of a database can be inconsistent while
+ snapshot is made. E.g. the files of a database can be inconsistent while
the database is running.</para>
<para>Consistency after undochange is not guaranteed. E.g. when the
<refsect1 id='description'>
<title>DESCRIPTION</title>
- <para>Snbk is a command-line program to backup snapshot of snapper. It can
+ <para>Snbk is a command-line program to backup snapshots of snapper. It can
transfer and delete backup snapshots on local and remote btrfs filesystems.</para>
</refsect1>
</programlisting>
</para>
<para>If the system was reinstalled it is unfortunately in general
- not possibly to simply use the restored snapshot as the new default
+ not possible to simply use the restored snapshot as the new default
snapshot since some files, e.g. /etc/fstab, likely need
modifications. Also unfortunately for other subvolumes than root a
rollback is not supported.</para>