The block count in the xattr doesn't amount to 16GB of used space.
Is this consistently reproducible? If it is, then could you share the steps?
That would help me recreate this in-house and debug it.
-Krutika
----- Original Message -----
> From: "Lindsay Mathieson" <lindsay.mathieson at gmail.com>
> To: "Krutika Dhananjay" <kdhananj at redhat.com>
> Cc: "gluster-users" <gluster-users at gluster.org>
> Sent: Tuesday, November 3, 2015 5:16:52 PM
> Subject: Re: [Gluster-users] Shard file size (gluster 3.7.5)
> On 3 November 2015 at 21:06, Krutika Dhananjay < kdhananj at redhat.com
> wrote:
> > OK. Could you share the xattr values of this image file?
>
> > # getfattr -d -m . -e hex <path-to-the-file-in-the-backend>
>
> gluster volume set datastore3 performance.strict-write-ordering on
> # rsync file to gluster mount
> # Size matches src file
> ls -l vm-301-disk-1.qcow2
> -rw-r--r-- 1 root root 27746172928 Nov 3 21:40 vm-301-disk-1.qcow2
> # Disk usage size is way to small, should be around 16GB
> du vm-301-disk-1.qcow2
> 390730 vm-301-disk-1.qcow2
> # Attributes of backend file
> getfattr -d -m . -e hex
> /glusterdata/datastore3/images/301/vm-301-disk-1.qcow2
> getfattr: Removing leading '/' from absolute path names
> # file: glusterdata/datastore3/images/301/vm-301-disk-1.qcow2
> trusted.afr.dirty=0x000000000000000000000000
> trusted.bit-rot.version=0x020000000000000056386f9400013a25
> trusted.gfid=0xc633865ef6ca4010a47cfc80d6c35331
> trusted.glusterfs.shard.block-size=0x0000000010000000
>
trusted.glusterfs.shard.file-size=0x0000000675cd0000000000000000000000000000000bec940000000000000000
> --
> Lindsay
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20151104/ee8d7f08/attachment.html>