Hi Wayne,
Thanks for the rapid fix.
That looks like it mostly fixed it. I was getting 100's and 100's of
mkdir warnings. Now I only get a single warning. The directory was a CVS
directory but I doubt that matters. Maybe there is another case you missed?
cheers
Stuart
On Tue, May 04, 2004 at 01:4
On Tue, May 04, 2004 at 01:41:04PM +1200, Stuart Inglis wrote:
> mkdir -p a/b/c
> then later on tries to create:
> mkdir -p a/b
Thanks for the clarification. I dug into this and I found that some of
the code paths try to call make_bak_dir() without first getting an
ENOENT error. This can cause t
When I perform a rsync with backup I get 100's of:
make_bak_dir mkdir "/export/giger.back.eary/java/weka/gui" failed:
File exists
make_bak_dir mkdir "/export/giger.backary/java/weka/gui" failed:
File exists
make_bak_dir mkdir "/export/giger.back...ary/java/weka/gui" failed: File
exists
On Tue, May 04, 2004 at 12:19:29PM +1200, Stuart Inglis wrote:
> make_bak_dir mkdir "/export/giger.back.eary/java/weka/gui" failed:
> File exists
Did you check that path? I assume there is a file that is in the way of
a directory that needs to be created. Perhaps this condition just
arose?
Previously I have been using 2.5.7 and have changed 2 days ago to 2.6.2.
Nothing else has changed, so I figured this was just an extra warning
added to 2.6.2.
I am backing up a 750G RAID array. Without knowing the details it's
almost like the --backup-dir option creates a subdirectory
mkdir -
