I'm running a single SAS drive as its own filesystem within ZFS and am encountering a really strange problem.
Background:
I recently acquired Seagate Cheetah ST3300557SS, which is 300GB SAS 6Gb/s drive with encryption. I have it connected to a BR10i in one of the channels along with 7 other SATA disks on PCIe x8 lanes on x9scm-f board. Running ZFS as vm in esxi, filesystem of the drive is shared NFS.
Problem:
While running a benchmark write test (dd if=/dev/zero) to fill the entire drive with 0s, the write performance goes from ~150MB/s all the way down to ~10MB/s at random intervals. I can't reproduce same behavior every time, but the write operation slows down the drive when the drive is around 20GB full and 50GB full.
Even when attempting to transfer large files into the drive the transferring speed drops down to less than 10MB/s at random times.
In theory, the drive shouldn't have any "slowdowns" of any kind. I'm completely confused because I can't find the source of the problem. I tried variations of memory to the OS from 2GB to 8GB and the number of CPUs/cores assigned to the vm with same results.
Anyone see this kind of behavior before? How the heck do I solve this thing?
Background:
I recently acquired Seagate Cheetah ST3300557SS, which is 300GB SAS 6Gb/s drive with encryption. I have it connected to a BR10i in one of the channels along with 7 other SATA disks on PCIe x8 lanes on x9scm-f board. Running ZFS as vm in esxi, filesystem of the drive is shared NFS.
Problem:
While running a benchmark write test (dd if=/dev/zero) to fill the entire drive with 0s, the write performance goes from ~150MB/s all the way down to ~10MB/s at random intervals. I can't reproduce same behavior every time, but the write operation slows down the drive when the drive is around 20GB full and 50GB full.
Even when attempting to transfer large files into the drive the transferring speed drops down to less than 10MB/s at random times.
In theory, the drive shouldn't have any "slowdowns" of any kind. I'm completely confused because I can't find the source of the problem. I tried variations of memory to the OS from 2GB to 8GB and the number of CPUs/cores assigned to the vm with same results.
Anyone see this kind of behavior before? How the heck do I solve this thing?