On Feb 18 2015, Guilherme Barile <[email protected]> wrote:
> Nikolaus,
>
> After fscking and upgrading my volume to the new db revision, I was
> able to mount the filesystem and access all the files without problems
> (even though I stress the filesystem a lot, I never lost data using
> s3ql).
>
> With the volume back online, I started to rsync about 280gb of files
> *from* S3QL to an EBS volume (everything running inside AWS, on the
> same region). I had 3 jobs in parallel - one syncing small videos
> (15000 ~100mb files), one syncing photos (15000 ~5mb files) and
> another one syncing a 3GB volume with about 100.000 small (10-500kb)
> files.
>
> The high io wait situation occurred after about 3 hours of processing.
> I use newrelic to monitor the server, so I could notice a spike of
> writes on my local cache disk, which I documented here -
> https://docs.google.com/document/d/1S927JPyMG4SCxkiIcReQDHWACM1qozYOMTa86pGQ1k4/edit?usp=sharing
What does ~/.s3ql/mount.log say?
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
