On Jan 25 2016, Igor Galić <[email protected]> wrote:
> Everything works super fine, except when it fails, then it fails horribly.
> Even just a shutdown of the vm (which, in theory, unmounts all file systems)
> will make it so that it's impossible to mount the fs on another machine:
>
> Backend reports that fs is still mounted elsewhere, aborting.
>
> What can i do in such situations?
Avoid them in the first place, by ensuring that file systems are
unmounted not just in theory but in practice.
If the damage is already done, you can get the file system mountable
again by running fsck.s3ql, but you will most likely loose data.
Best,
-Nikolaus
(No Cc on replies please, I'm reading the list)
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
