>> ... I can demonstrate one (perhaps pathological) case where Time Machine fails to back up a file.
> Alan originally contacted me about this issue, and I can now confirm that the scenario he described is a pretty serious problem.
We are aware that it's a real problem but the question
is how common is this scenario? To us it seems quite
unusual to rename a directory, do stuff inside it,
rename it back *and* do nothing else that would bump
the mtime on the directory.
> I'm actually rather surprised this is happening. When I talked to an Apple Engineer at the time when Time Machine was introduced (WWDC 2006?), I though they said that the FSEvents were tracked using the nodeID of the modified directory, not its path. So the path reported in the historic event stream should be the path of the modified folder as it exists now (i.e. Users/james/Desktop/Test/a/b/c/d/e/), not its path when it was modified (i.e. not Users/james/Desktop/Test/x/b/c/d/e/).
I'm not sure how told you that but it's not true. It
has been proposed as a possible solution but you can't
just do that since when a file is deleted you want to
know about that but there's not inode number any more.
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden