Jeff Bogatay <j...@bogatay.com> writes:
> I am in the process of crafting a s3ql backed backup solution. During
> the development/testing I left the store mounted, installed some
> system updates and rebooted.
>
> Now I am unable to mount and/or check the store. Running 2.12 on
> ArchLinux. It has been several hours since I last wrote to the store.
>
> My last attempt was to delete the local metadata and have it rebuilt.
> Same error as below.
>
> Not sure what to do next or how to recover. Are these stores typically
> this fragile?
What do you mean with "the store"? Are you talking about a remote
storage server? In that case the fragility obviously depends on the
server.
> Also, as a test I created a fresh mount, wrote to it, unmounted it,
> and remounted it without any issues.
>
> 2015-02-04 16:56:35.635 9617:MainThread s3ql.deltadump.dump_metadata:
> dump_table(ext_attributes): writing 0 rows
[...]
I am not sure what I'm looking at here. First you say it works, but then
you quote an error message (and the formatting is pretty messed
up). Can you be more precise as to when exactly the error occurs (and is
it always the same)?
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to s3ql+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
