On Oct 20 2016, jingjie li <[email protected]> wrote:
> ＞The only situation where S3QL creates an object that contains only
> zeros
> ＞is if you created a file (inside the S3QL file system) that contains
> ＞that many zeros.
>
> I don’t create an object that contains only zeros.
Maybe you don't, but whatever application you use to copy & paste the
file does.
> In the beginning of transferred a file that size > max_object_size,
> S3QL truncate an object that contains only zeros, and set dirty flag
> to True in s3ql.block_cache.truncate() function.
>
> This is only happened in the way that copy&paste a file that size is
> greater than max_object_size from win7 by samba.
Which should tell you that this is not a problem with S3QL.
> I want to avoid this problem by the way below, please help me to
> confirm that is it OK? it will cause other problems or not?
It will cause problems. It means that if you truncate (or extend) a file
and unmount the file system, the change will be lost. On the next mount,
the file will have the original size again. And if you attempt to read
the complete file, you will get a crash because the storage objects are
missing.
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.
