Using 'o' in the fileset accurate option has caused problems with restore for
another user on the list recently. I don't know if it could also break
estimate. Have you used the 'o' option in previous incremental backups?
Accurate backups assume that the full path to each file is the same as befo
On 12/12/24 10:28 PM, Marcin Haba wrote:
Hello Everybody,
Yes, Bill. I will try to add my two cents :-)
Your notice about too long mtime is fully right. It is because the
lstat string is broken. Two lstat values are joined together and it
causes this wrong result. If we split them, then the d
Hi all,
Am 13.12.2024 um 13:01 schrieb Martin Simmons:
On Fri, 13 Dec 2024 10:23:18 +0100, Arno Lehmann via Bacula-users said:
As I couldn't really understand what Martin referred to I had another,
closer look :-)
I noticed that Bill's decoded lstats ended up with ctimes of 0 which is
some
I decoded the correct lstat values using bconsole and compared them. It
appears that only ctime and atime are different. The ctime for the file
changed in november. I must have done a chmod or something that changed
file metadata.
Given the small number of impacted files, and the fact that permiss
Hi Rob, all,
Am 13.12.2024 um 13:02 schrieb Rob Gerber:
Everyone,
Thank you very much for all the help with this interesting problem and
for your advice.
Arno,
that query very quickly returned 443123 lines. Looking through them,
some were longer than others.
Indeed. the 59 characters was n
Martin,
I think you are right. I repeated my first query, requesting just the lstat
field and the fields are not joined.
In fact, I think I may have introduced this error myself, because the lines
for the original query were originally printed 'wrapped', and I cleaned
them up in a text editor to
Everyone,
Thank you very much for all the help with this interesting problem and for
your advice.
Arno,
that query very quickly returned 443123 lines. Looking through them, some
were longer than others.
I wanted to count total entries for lstat, and they number around 2
million. So your query acc
> On Fri, 13 Dec 2024 10:23:18 +0100, Arno Lehmann via Bacula-users said:
>
> Hi all,
>
> Am 13.12.2024 um 06:28 schrieb Marcin Haba:
> ...
> > Your notice about too long mtime is fully right. It is because the
> > lstat string is broken. Two lstat values are joined together and it
> > causes
Hi all,
Am 13.12.2024 um 06:28 schrieb Marcin Haba:
...
Your notice about too long mtime is fully right. It is because the
lstat string is broken. Two lstat values are joined together and it
causes this wrong result. If we split them, then the decoded values
are more realistic and the number of
