I noticed that several sharding bugs relating to file size got closed because 3.7.4 got released. However, file sizes are still messed up in 3.7.4. I know this is a beta feature, but you cannot even write a single file without getting the wrong file size.
Neither buffered or direct IO works: # dd if=/dev/zero of=/voltest/dd.buffered bs=1024k count=1024 1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB) copied, 1.66046 s, 647 MB/s # dd if=/dev/zero of=/voltest/dd.direct oflag=direct bs=1024k count=1024 1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB) copied, 1.91092 s, 562 MB/s root@science08:~/test# ls -l /voltest total 2104384 -rw-r--r-- 1 root root 1075052544 Sep 14 14:31 dd.direct -rw-r--r-- 1 root root 1074266112 Sep 14 14:18 dd.buffered # gluster vol info voltest Volume Name: voltest Type: Distribute Volume ID: 849e2d6b-faaa-43d7-b06e-3c6d3057dff3 Status: Started Number of Bricks: 4 Transport-type: tcp Bricks: Brick1: sc03:/brick_ssd_0/gv Brick2: sc04:/brick_ssd_0/gv Brick3: sc03:/brick_ssd_1/gv Brick4: sc04:/brick_ssd_1/gv Options Reconfigured: features.shard: on performance.readdir-ahead: on root@science03:~# gluster --version glusterfs 3.7.4 built on Sep 1 2015 12:08:58
_______________________________________________ Gluster-users mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-users
