[Gluster-users] Shard file size (gluster 3.7.5)

Lindsay Mathieson lindsay.mathieson at gmail.com
Tue Nov 3 04:57:25 UTC 2015


md5sum matches too:

Volume Name: datastore3
Type: Replicate
Volume ID: def21ef7-37b5-4f44-a2cd-8e722fc40b24
Status: Started
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: vna.proxmox.softlog:/zfs_vm/datastore3
Brick2: vnb.proxmox.softlog:/glusterdata/datastore3
Brick3: vng.proxmox.softlog:/glusterdata/datastore3
Options Reconfigured:
performance.strict-write-ordering: on
features.shard-block-size: 256MB
features.shard: on
cluster.quorum-type: auto
performance.readdir-ahead: off
performance.cache-size: 1GB
performance.write-behind: on
performance.write-behind-window-size: 128MB
performance.io-thread-count: 32
nfs.enable-ino32: off
nfs.addr-namelookup: off
nfs.disable: off
performance.cache-refresh-timeout: 4
cluster.server-quorum-ratio: 51%

On 3 November 2015 at 14:51, Lindsay Mathieson <lindsay.mathieson at gmail.com>
wrote:

>
> On 3 November 2015 at 14:28, Krutika Dhananjay <kdhananj at redhat.com>
> wrote:
>
>> Correction. The option needs to be enabled and not disabled.
>>
>> # gluster volume set <VOL> performance.strict-write-ordering on
>>
>
>
> That seems to have made the difference, exact match in size bytes to the
> src file. I'll do a md5sum as well
>
>
> --
> Lindsay
>



-- 
Lindsay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20151103/88a59b41/attachment.html>


More information about the Gluster-users mailing list