search for: 247g

.../tmp /dev/mapper/kvm01--vg-var 9.2G 302M 8.4G 4% /var /dev/sda1 236M 63M 161M 28% /boot tmpfs 1.6G 4.0K 1.6G 1% /run/user/115 tmpfs 1.6G 0 1.6G 0% /run/user/1000 glusterp1.graywitch.co.nz:/gv0 932G 247G 685G 27% /isos also, I can mount the sub-directory fine on the gluster cluster itself, ======= [root at glustep1 libvirt]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/centos-root 20G 3.4G 17G 17% / devtmpfs...

...4M 1.5T 1% /share /dev/mapper/centos-home 1.8T 5.5G 1.7T 1% /home /dev/sda1 497M 158M 340M 32% /boot tmpfs 13G 32K 13G 1% /run/user/1000 tmpfs 13G 36K 13G 1% /run/user/0 /dev/sde 917G 625G 247G 72% /media/usb [root at localhost ~]# fdisk -l /dev/sdc fdisk: cannot open /dev/sdc: Input/output error [root at localhost ~]# ------------------------------ Regards Hersh

Currently I''m trying to figure out the best zfs layout for a thumper wrt. to read AND write performance. I did some simple mkfile 512G tests and found out, that per average ~ 500 MB/s seems to be the maximum on can reach (tried initial default setup, all 46 HDDs as R0, etc.). According to http://www.amd.com/us-en/assets/content_type/DownloadableAssets/ArchitectureWP_062806.pdf I would

...= 1 (out [1], left {60, 0}) write(1, "\35\0\0\0", 4) = 4 select(1, [0], [], NULL, {60, 0}) = 1 (in [0], left {59, 658000}) read(0, "\36\0\0\0", 4) = 4 select(2, NULL, [1], [1], {60, 0}) = 1 (out [1], left {60, 0}) write(1, "G\221\247G", 4) = 4 select(1, [0], [], NULL, {60, 0}) = 1 (in [0], left {59, 140000}) read(0, "\0\0\0\0", 4) = 4 lstat("/reference/Quality/Issue14", {st_mode=S_IFDIR|0775, st_size=4096, ...}) = 0 chdir("/reference/Quality") =...