Recent content by Romjo

Oh thheo, its still set to write through and no read ahead... Will normal disk cache cause issues like this still? Sent from my Nexus 5 using Tapatalk

So now the server seems very quick and stable.. Although we're probably looking to upgrade the raid cards soon. For now I've set a cron job to set the disk cache on with every reboot. I realized that even though megacli kept reporting that it was enabled, it wasn't. Since we've taken one node...

Updated Disk Firmware and played with these settings.... Same Raid 10, 10 Disks root@prox31:/home# megacli -LDSetProp disDskCache -LAll -aAll Set Disk Cache Policy to Disabled on Adapter 0, VD 0 (target id: 0) success Exit Code: 0x00 root@prox31:/home# pveperf /var/lib/vz CPU BOGOMIPS...

No, this is 10 active disks. No spares. I have two disks out of raid so I can do the install on a separate disk and testing with an untaxed single disk. Sent from my Nexus 5 using Tapatalk

Single Disk /dev/sdb root@prox31:~# fio /usr/share/doc/fio/examples/iometer-file-access-server iometer: (g=0): rw=randrw, bs=512-64K/512-64K, ioengine=libaio, iodepth=64 2.0.8 Starting 1 process iometer: Laying out IO file(s) (1 file(s) / 4096MB) Jobs: 1 (f=1): [m] [100.0% done] [723K/177K...

I reinstalled the entire server to test the hardware. Breaking the existing raid, used the latest version of proxmox if the older version was the issue Sent from my Nexus 5 using Tapatalk

I used the default proxmox 3.1. Ext3. Mounted the other disks using the regular mount command. Mount /Dev/sdx /var/lib/vz Sent from my Nexus 5 using Tapatalk

Disk0 - Same As Proxmox install. Disk 0CPU BOGOMIPS: 63999.52 REGEX/SECOND: 1247555 HD SIZE: 68.66 GB (/dev/mapper/pve-root) BUFFERED READS: 153.33 MB/sec AVERAGE SEEK TIME: 6.72 ms FSYNCS/SECOND: 47.75 DNS EXT: 146.81 ms DNS INT: 0.82 ms Disk1 -...

Wasn't sure if there was some sort of polling that would affect the disks. Anyhow I'm bringing down the server today so I'll be able to update firmware and break the raid. Sent from my Nexus 5 using Tapatalk

Would Time have any affect on this performance (detrimentally so?), time was off between nodes by 3 minutes. My test so far has been W2k8 install times, I tested this with *RAW format and it was pretty quick compared to *VMDK which was taking around 2 hours. Haven't re-tested with *VMDK with...

Yeah I know it does, that's why im worried about the performance! haha. Not in office now, but I can pull the data again when I go there. From a few posts up: ~# megaclisas-status-- Controller informations -- -- ID | Model c0 | PERC H310 Mini -- Arrays informations -- -- ID | Type | Size |...

Okay so i've run fio without anything running - even did a reboot and made sure no VMs were started. # fio /usr/share/doc/fio/examples/iometer-file-access-serveriometer: (g=0): rw=randrw, bs=512-64K/512-64K, ioengine=libaio, iodepth=64 Starting 1 process Jobs: 1 (f=1): [m] [100.0% done]...

Megaclisas-status Sry they're 300G. ~# megaclisas-status-- Controller informations -- -- ID | Model c0 | PERC H310 Mini -- Arrays informations -- -- ID | Type | Size | Status | InProgress c0u0 | RAID10 | 1633G | Optimal | None -- Disks informations -- ID | Model | Status c0u0p0 | WD...

PVEPerf with just the 1 Linux FW running. # pveperf /var/lib/vzCPU BOGOMIPS: 63990.69 REGEX/SECOND: 1037632 HD SIZE: 1443.74 GB (/dev/mapper/pve-data) BUFFERED READS: 496.27 MB/sec AVERAGE SEEK TIME: 7.37 ms FSYNCS/SECOND: 45.67 DNS EXT: 4011.20 ms DNS INT...

Sry about that, Primary VM with the issue VM211: VM211 File Server boot: cdn bootdisk: virtio0 cores: 2 ide2: none,media=cdrom memory: 4096 name: <Removed> net0: e1000=<Removed>,bridge=vmbr0 onboot: 1 ostype: wxp sockets: 1 virtio0: local:211/vm-211-disk-1.vmdk virtio1...