Hi Raquel I'm pretty new to this too but from what I can tell the files are broken into blocks encrypted and compressed before they are moved into S3.
This means that the files in S3 are useless to you unless you view them through your mount point inside the server. So on your server you can see image.jpg but the minute you upload it to s3 it's broken into pieces and only reassembled on download. So answering your questions: 1. These files are system files for that s3ql uses to get encryption keys etc, when you upload files they will be broken down into similar chunks. 2. You have pushed the data so long as you can see it in your mounted directory, but because of how s3ql works you won't be able to access the data through the s3 console. 3. Again it will be broken down into chunks and save as chunks, not as a full image. Hope this helps GIles On Friday, 17 October 2014 14:43:53 UTC+1, Raquel Carrillo wrote: > > Good afternoon, everyone! > > It's my first time, so hopefully you can help me out. > > Lately I have been experimenting with Amazon S3 and s3ql, I need to mount > the bucket on ec2 and to access the data ( write/read ) stored on it like > files,images, videos etc. > > I have followed the instructions on > https://groups.google.com/forum/#!topic/s3ql/uUAnL3Rd4bM , which by the > way worked great!! > > I have accomplished to mount the filesystem, but I have a few dudes: > > sudo mkfs.s3ql --plain --force s3://container Enter backend login: asdf > Enter backend password: asdf Before using S3QL, make sure to read the > user's guide, especially the 'Important Rules to Avoid Loosing Data' > section. Purging existing file system data.. Please note that the new file > system may appear inconsistent for a while until the removals have > propagated through the backend. Creating metadata tables... Dumping > metadata... ..objects.. ..blocks.. ..inodes.. ..inode_blocks.. > ..symlink_targets.. ..names.. ..contents.. ..ext_attributes.. Compressing > and uploading metadata... Wrote 0.00 MB of compressed metadata. > > sudo mount.s3ql --allow-other s3://container /mnt/s3ql Using 10 upload > threads. Enter backend login: asdf Enter backend password: asdf Using > cached metadata. Mounting filesystem... > > 1. > > When list (ls) the contents of the mounted directory, using de > commandline in ec2, all that shows to me is lost+found. But When I see the > content of the bucket using the web console in s3 I see files like: > s3ql_metadata s3ql_seq_no_1 Why can't I see these files on my mounted > directory? and what do they represent? > 2. > > I made a new directory, using commandline in the s3ql directory with: > sudo mkdir test-dir sudo touch testfile.txt > > But I can't see these files in the web console of my bucket in s3. > > Am I missing something? how do I push data towards s3 If I already mount > the bucket on the ec2. Do I have to use s3qlctrl to push data? > > 3- This one is conceptual if for example I need to save my_photo.jpg in > the bucket and I use s3ql, the file will be saved, and I will be able to > see it with the web console like "my_photo.jpg " or it will be saved in > another format? > > I would really appreciate your help! > -- 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.
