Yes, that's what I expect. I wasn't sure what Daniel was claiming.
__Martin
> On Tue, 13 Feb 2024 16:23:11 +, Chris Wilkinson said:
>
> Well, yes and no. From what I see;
>
> mv on a file will update ctime as expected.
>
> mv of a directory will update the directory ctime but not tha
Well, yes and no. From what I see;
mv on a file will update ctime as expected.
mv of a directory will update the directory ctime but not that of any
contained files or directories.
This is on debian 11.
-Chris-
On Tue, 13 Feb 2024, 16:01 Martin Simmons, wrote:
> Are you saying that mv on a f
Are you saying that mv on a file doesn't change the ctime? If so, which
filesystem is that please?
__Martin
> On Mon, 12 Feb 2024 22:52:08 +0100, Daniel Etter said:
>
> mv does not change the dates, only cp change the time, because it is a new
> file.
>
> Daniel
>
>
>
> Am Mo., 12. Feb
Ah, yes, it won't work for the inner files if you mv a subdirectory. Using
the accurate flag is the way to go.
__Martin
> On Mon, 12 Feb 2024 21:36:07 +, Chris Wilkinson said:
>
> I don't have mtimeonly set.
>
> I mv'd a sample file in my home directory as an experiment and saw that
>
mv does not change the dates, only cp change the time, because it is a new
file.
Daniel
Am Mo., 12. Feb. 2024 um 22:39 Uhr schrieb Chris Wilkinson <
winstonia...@gmail.com>:
> I don't have mtimeonly set.
>
> I mv'd a sample file in my home directory as an experiment and saw that
> stat reports
I don't have mtimeonly set.
I mv'd a sample file in my home directory as an experiment and saw that
stat reports that atime, mtime remain unchanged but ctime does change as
you expected.
When I stat one of the files I moved before, I see that ctime did not
change.
I had previously mv'd a whole s
Do you have the mtimeonly option set in the FileSet?
I would expect mv to change the ctime. Can you repeat this (mv not changing
the ctime)?
__Martin
> On Sun, 11 Feb 2024 09:17:10 +, Chris Wilkinson said:
>
> I'm seeing that files that are mv'd within the same folder are not being
>
Yes I'm sorry I wasn't clear. I meant moved from one folder to another but
still within the backed up folder. The name, ctime, atime all remain
unchanged.
I'll give the accurate flag a try.
Chris
On Sun, 11 Feb 2024, 10:02 Matlink, wrote:
> What do you mean by "moved within the same folder"?
What do you mean by "moved within the same folder"? Do you mean renamed?
Bacula does inaccurate incrementals and differentials, which means it does not
try to check if files have been moved across folders. This is for performance
matters. However, if it matters to you, this is configurable (Accu
I'm seeing that files that are mv'd within the same folder are not being
backed up by incr or diff backups. This is on Bacula v11, Debian 11.
I'm guessing that this is because mtime and ctime are unchanged by mv and
that the full path is not used.
This is not a big problem I suppose because the f
10 matches
Mail list logo
