Re: [ARMini-support] SafeStore Question
- From: John Harrison <john@xxxxxxxxxxxxxxxx>
- To: armini-support@xxxxxxxxxxxxx
- Date: Mon, 31 Jul 2017 22:40:35 +0100
In article <gemini.otyp5800hckbu01x0.alan@xxxxxxxxxxxxxxx>,
Alan Wrigley <alan@xxxxxxxxxxxxxxx> wrote:
It appears that if you have replaced a directory with a file of the same
name, the next time that backup job is run you will get a "tree
corrupted" error. In fact the tree isn't corrupted at that point;
SafeStore merely thinks it is.
The symptom is familiar but the interpretation doesn't fit completely.
AFIA I have never created a file with the same name as a directory, because
if I tried to do so I would get an error message.
One way it sometimes happens is if I upgrade some software and the
supporting files have been re-arranged with several files in a directory
named X rather than a file named X. But again this shows up when I do the
upgrade.
Although my 'whole disk' backup obviously contains lots of Apps, the job I
most regularly run, and which is currently corrupted, is my working
documents, which contains no Apps (other than the odd Basic program that
hasn't changed for years).
So how do I get the error: 'a directory with that name already exists'
error? Typically it is when I need to do a backup, discover a corruption
but haven't got time to run the job from scratch. So I did a quick and
dirty copy of what I think are the directories likely to have most
important material in them. Typically while doing so I get one or more
'directory exists' error. By then I'm under considerable time pressure
(aka getting desperate) so I just skip each one without investigating in
order to copy as much as possible.
If/when it happens again I'll try to investigate.
NB, just to clarify, I have never had any indication of that problem when
running backups, only when doing bulk manual copies.
--
John Harrison
Website
http://jaharrison.me.uk
---
To alter your preferences or leave the group,
visit
//www.freelists.org/list/armini-support
List-related queries to info@xxxxxxxxxxxx
Other related posts:
