Hi Adrian ,
Thanks for your explanation ...
About Q2 , manifest question
Is there any audit mechanism to delete segments of failure uploading object?
What if the uploading procedure is been interrupted by user .
As you said , I think the segments still available for accessing .
On the other hand
On 18/06/12 11:57, Kuo Hugo wrote:
Hi Adrian ,
Thanks for your explanation ...
About Q2 , manifest question
Is there any audit mechanism to delete segments of failure uploading object?
What if the uploading procedure is been interrupted by user .
As you said , I think the segments
Hi folks ,
Q1:
Where's the metadata of an object ?
For example the X-Object-Manifest. Does it store in inode ?
I did not see the matadata X-Object=Manifest in container's DB.
Could I find the value?
Q2:
What if a large object be interrupted during upload , will the manifest
objects be deleted?
Q1: Where's the metadata of an object ?
It's stored in extended attributes on the filesystem itself. This is
reason XFS (or other filesystem supporting extended attributes) is
required.
Could I find the value?
Sure. You just need some way of a) identifying the object on disk and,
b) a means of
4 matches
Mail list logo