Re: [ARMini-support] SafeStore Question
- From: Richard Porter <ricp@xxxxxxxxxxxxxxxx>
- To: armini-support@xxxxxxxxxxxxx
- Date: Tue, 25 Jul 2017 11:50:22 +0100
On 25 Jul 2017 lists (Stuart) wrote:
In article <d2f9475256.ricp@xxxxxxxxxxxxxxxxxxxxx>,
Richard Porter <ricp@xxxxxxxxxxxxxxxx> wrote:
SafeStore is prone to corrupting its tree files, not just on ARMX6.
Usually it just misses out lines, which can be recovered if you add
the missing <dir> and </dir> lines. I assume any missing file tags
will just result in those files being treated as new. Unfortunately
when it starts setting all the stamps to zero there's not a lot you
can do.
Is that the cause of "The file list has become corrupted" error which I
see far too often when it is trying to back up my complete main drive,
(with some directories such as !Scrap ignored). I doubt it successfully
backs up more than about three times without falling over and "force"
never does anything.
Yes. It's seen a change of indentation with no <dir> or </dir> tag.
The indentation increases by 2 spaces after <dir...> and reduces by 2
after </dir>. I've never seen incorrect indentation.
I have to delete the job and create a new one every time.
You can edit the tree file but it's tedious. The first error will be
at a line number greater than the number of files processed when the
error occurs, but further lines are likely to be missing up to the end
of the file. It would be useful if the error message contained the
line number. I've been contemplating writing a little basic program to
pinpoint all the errors.
Another approach is to save a copy of a good tree file, then you can
copy it back in place of a bad one. That may result if a few files
being backed up again but that's no big deal.
Richard
--
Richard Porter
http://www.minijem.plus.com/
t: @westernexplorer
mailto:ricp@xxxxxxxxxxxxxxxx
I don't want a "user experience" - I just want stuff that works.
---
To alter your preferences or leave the group,
visit
//www.freelists.org/list/armini-support
List-related queries to info@xxxxxxxxxxxx
Other related posts:
