A picture says a thousand words, so I thought I'd wrap this discussion up with a KVM windows server disk performance screenshot. Very good results.
Greg J. Zartman, P.E. President, Principal Engineer LEI Engineering & Surveying, LLC 2160 Davcor Street SE Salem, Oregon 97302 Office: 541-683-8383 (ext 103) Cell: 541-521-8449 Fax: 866-232-6790 www.leiengineering.com SBA Certified HUBZone Contractor On Thu, Jan 22, 2015 at 10:59 AM, Greg Zartman <[email protected]> wrote: > On Thu, Jan 22, 2015 at 10:47 AM, Kim Culhan <[email protected]> wrote: > >> >> What method did you use to locate the bad device ? >> > > I did a: iostat -xnc 1 in the global zone. I then went into the Centos > KVM in a separate terminal and did a "dd" write to the NFS volume in > question. Watching the global zone terminal iostate output, I monitored > what the %b (% busy) output was for each drive. One of the spindle drives > was maxed at 100%. Sigxcpu (IRC username) suggested that this was the bad > drive and I should try detaching it (This was one drive in a mirrored > vdev). I then did a zpool detach zones <suspected bad device>. I then > went back to my KVM termainal and re-initiated the dd write test. iostate > in the global zone then showed even %b across all devices and my dd write > test in the KVM reported a really good write speed to the NFS volume. > > Hope that helps. > > Greg > > ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
