search

google-code-export / s3ql

Automatically exported from code.google.com/p/s3ql
0 stars 0 forks source link

Allow accessing file systems with corrupted backends #389

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Currently S3QL unmounts if it detects corruption in the backend. This is great, 
because it ensures that the problem gets noticed. It's rather annoying once the 
problem has been noticed and the still intact data is to be retrieved though.

mount.s3ql should get a --recovery option that mounts the file system read only 
and just gives read errors for corrupted data. That way, a simple rsync or cp 
call can be used to retrieve everything from the backend that's still intact.

Original issue reported on code.google.com by Nikolaus@rath.org on 22 Jan 2013 at 3:30

GoogleCodeExporter commented 9 years ago 
... or maybe we can just issue error messages without unmounting once issue 362 
is fixed?

Original comment by Nikolaus@rath.org on 23 Jan 2013 at 2:21

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision a20d27b93486.

Original comment by Nikolaus@rath.org on 4 May 2013 at 10:06