search for: 407m

I installed Centos 6.x 64 bit with the minimal ISO and used two disks in RAID 1 array. Filesystem Size Used Avail Use% Mounted on /dev/md2 97G 918M 91G 1% / tmpfs 16G 0 16G 0% /dev/shm /dev/md1 485M 54M 407M 12% /boot /dev/md3 3.4T 198M 3.2T 1% /vz Personalities : [raid1] md1 : active raid1 sda1[0] sdb1[1] 511936 blocks super 1.0 [2/2] [UU] md3 : active raid1 sda4[0] sdb4[1] 3672901440 blocks super 1.1 [2/2] [UU] bitmap: 0/28 pages [0KB], 65536KB chunk md2 : active raid1...

..../51/msg/5 238M ./51/msg/1 271M ./51/msg/3 3.3G ./51/msg 3.3G ./51 after changing the directory and running du again I get different numbers #cd 51 du -h 306M ./msg/8 676M ./msg/9 351M ./msg/6 338M ./msg/0 347M ./msg/10 394M ./msg/2 480M ./msg/7 544M ./msg/4 407M ./msg/11 312M ./msg/5 326M ./msg/1 377M ./msg/3 4.8G ./msg 4.8G . Do you have any idea what could cause this behaviour?

...e I had to shut down the virtual machine and do this while being offline. Thanks Wang for your valuable input. As far as the memory goes, there's plenty of head room: $ free -h total used free shared buff/cache available Mem: 7.8G 1.8G 407M 9.7M 5.5G 5.5G Swap: 8.0G 619M 7.4G 2017-07-02 10:26 GMT+02:00 王李明 <wanglm@certusnet.com.cn>: > mybe this is because you physic host memory is small > > then this will Causing instability of the virtual machine > > But I'm just guessin...

...20 0 392m 41m 1616 S 10 0.3 252:44.63 glusterfsd 2496 root 20 0 392m 41m 1544 S 10 0.3 262:26.80 glusterfsd 2478 root 20 0 392m 41m 1536 S 9 0.3 219:15.17 glusterfsd 2508 root 20 0 585m 365m 1364 S 5 2.3 46:20.31 glusterfs 3081 root 20 0 407m 101m 1676 S 2 0.6 239:36.76 glusterfs

...d do this while being > offline. > > Thanks Wang for your valuable input. As far as the memory goes, there's > plenty of head room: > > $ free -h > total used free shared buff/cache > available > Mem: 7.8G 1.8G 407M 9.7M 5.5G > 5.5G > Swap: 8.0G 619M 7.4G > > 2017-07-02 10:26 GMT+02:00 王李明 <wanglm@certusnet.com.cn>: > >> mybe this is because you physic host memory is small >> >> then this will Causing instability of the virtual machine...

...anks Wang for your valuable input. As far as the memory goes, there's >>> plenty of head room: >>> >>> $ free -h >>> total used free shared buff/cache >>> available >>> Mem: 7.8G 1.8G 407M 9.7M >>> 5.5G 5.5G >>> Swap: 8.0G 619M 7.4G >>> >>> 2017-07-02 10:26 GMT+02:00 王李明 <wanglm@certusnet.com.cn>: >>> >>>> mybe this is because you physic host memory is small >>>> >>&g...

Hi again, just today an issue I've thought to be resolved popped up again. We backup the machine by doing: virsh snapshot-create-as --domain domain --name backup --no-metadata --atomic --disk-only --diskspec hda,snapshot=external # backup hda.qcow2 virsh blockcommit domain hda --active --pivot Every now and then this process fails with the following error message: error: failed to pivot

Running a zpool scrub on our production pool is showing a scrub rate of about 400K/s. (When this pool was first set up we saw rates in the MB/s range during a scrub). Both zpool iostat and an iostat -Xn show lots of idle disk times, no above average service times, no abnormally high busy percentages. Load on the box is .59. 8 x 3GHz, 32GB ram, 96 spindles arranged into raidz zdevs on OI 147.

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