On Sat, Jun 15, 2019 at 20:35:30 +0200, Uwe Menges wrote:
> On 6/15/19 6:43 PM, Jim Kusznir wrote:
> > Ever since, any backup is run as a level 0 (even though it reports doing
> > a level 1, 2, etc). Everything runs as 0.
> >
> > How do I fix this?
>
> I fixed a similar symptom on my system with
> property "CHECK-DEVICE" "NO"
> (using amgtar), which hands "--no-check-device" to GNU tar,
> which makes it no longer think the toplevel dir has been renamed,
> so it doesn't store all files in its incremental.
Yes, if the device for the filesystems in question are changing from
boot to boot, then using the --no-check-device option is necessary to
allow the incrementals to work as expected across reboots. But I
believe that option is not available for the GNUTAR application, so
assuming Jim is indeed using GNUTAR then it seems worth making sure
that's actually his problem before trying to implement that particular
solution....
> I think what happened to me is that some LVM volumes got mounted with a
> different minor number, triggering that.
>
> Given that LVM is really common nowadays, I wonder if that option should
> be default.. I can't think of a use case where the current default is
> preferable, at the moment.
Yes. In particular, as long as --one-file-system is passed to GNU tar
(the default situation in Amanda) then every file backed up by that run
of tar is going to be on one single device, and the check-device
operation when building the list of incremental changes is never going
to be useful. (And obviously, in the case of changed device numbers for
the filesystem, the check is actually harmful).
I don't know about changing the actual default in the amgtar application
itself at this point in time, but perhaps it at least makes sense to
recommend disabling check-device in the example amanda.conf and other
documentation....
Nathan
----------------------------------------------------------------------------
Nathan Stratton Treadway - [email protected] - Mid-Atlantic region
Ray Ontko & Co. - Software consulting services - http://www.ontko.com/
GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239
Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
