I have a backup that involves mounting an s3ql file system and using
'rsync --delete ...' to do the backup.
If a large folder (or file) is moved, there is a risk that the files will
be 'deleted' before they area created again, possibly resulting in remote
data being deleted then recreated.
Is
lol...that works...didn't know it existed. Thank you!
On Tuesday, January 5, 2021 at 7:09:25 PM UTC+11 Cliff Stanford wrote:
> On 05/01/2021 05:42, rabidmuta...@gmail.com wrote:
>
> > If a large folder (or file) is moved, there is a risk that the files
> > will be &#x
This is a little sad, but my host has pythion3.6 as the default python, and
I use python3.11 for the build.
However, all of the build scripts use `#$! ... python3` which starts 3.6.
Is there any way that I can get the build process to either set he python
version in the "#!" for each file (3.1
Best,
> Nikolaus
>
> On Thu, 18 Apr 2024, at 07:42, rabidmuta...@gmail.com wrote:
>
> This is a little sad, but my host has pythion3.6 as the default python,
> and I use python3.11 for the build.
>
> However, all of the build scripts use `#$! ... python3` which starts
:35:30 AM UTC+11 Daniel Jagszent wrote:
> Hello,
> Am 10.01.25 um 07:13 schrieb rabidmuta...@gmail.com:
>
> Corrupt remote data; what is the recommended recovery procedure?
>
> I found this:
> https://groups.google.com/g/s3ql/c/4LM5-5uXfQY/m/6amCKocRAQAJ
>
>
Corrupt remote data; what is the recommended recovery procedure?
I found this: https://groups.google.com/g/s3ql/c/4LM5-5uXfQY/m/6amCKocRAQAJ
...is it the best approach?
fsck.s3ql
Starting fsck of
Using cached metadata.
File system was not unmounted cleanly
Checking DB integrity...
Verifying
