On Wed, Apr 20, 2016 at 4:17 AM, qingwei wei <tchengwee@xxxxxxxxx> wrote: > Gluster volume configuration, those bold entries are the initial settings i > have > > Volume Name: g37test > Type: Stripe > Volume ID: 3f9dae3d-08f9-4321-aeac-67f44c7eb1ac > Status: Created > Number of Bricks: 1 x 10 = 10 > Transport-type: tcp > Bricks: > Brick1: 192.168.123.4:/mnt/sdb_mssd/data > Brick2: 192.168.123.4:/mnt/sdc_mssd/data > Brick3: 192.168.123.4:/mnt/sdd_mssd/data > Brick4: 192.168.123.4:/mnt/sde_mssd/data > Brick5: 192.168.123.4:/mnt/sdf_mssd/data > Brick6: 192.168.123.4:/mnt/sdg_mssd/data > Brick7: 192.168.123.4:/mnt/sdh_mssd/data > Brick8: 192.168.123.4:/mnt/sdj_mssd/data > Brick9: 192.168.123.4:/mnt/sdm_mssd/data > Brick10: 192.168.123.4:/mnt/sdn_mssd/data > Options Reconfigured: > server.allow-insecure: on > storage.owner-uid: 165 > storage.owner-gid: 165 > performance.quick-read: off > performance.io-cache: off > performance.read-ahead: off > performance.stat-prefetch: off > cluster.eager-lock: enable > network.remote-dio: enable > cluster.quorum-type: auto > cluster.server-quorum-type: server > nfs.disable: true > I notice that you are using a stripe volume. Would it be possible to test with a sharded volume? We will be focusing only on sharded volumes for VM disks going forward. Thanks, Vijay _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
