Kaydol

Flood göndermek, insanların floodlarını okumak ve diğer insanlarla bağlantı kurmak için sosyal Floodlar ve Flood Yanıtları Motorumuza kaydolun.

Oturum aç

Flood göndermek, insanların floodlarını okumak ve diğer insanlarla bağlantı kurmak için sosyal Floodlar ve Flood Yanıtları Motorumuza giriş yapın.

Şifremi hatırlamıyorum

Şifreni mi unuttun? Lütfen e-mail adresinizi giriniz. Bir bağlantı alacaksınız ve e-posta yoluyla yeni bir şifre oluşturacaksınız.

3 ve kadim dostu 1 olan sj'yi rakamla giriniz. ( 31 )

Üzgünüz, Flood yazma yetkiniz yok, Flood girmek için giriş yapmalısınız.

Lütfen bu Floodun neden bildirilmesi gerektiğini düşündüğünüzü kısaca açıklayın.

Lütfen bu cevabın neden bildirilmesi gerektiğini kısaca açıklayın.

Please briefly explain why you feel this user should be reported.

Learning the hard way about iscsi

Hello readers,

I pulled some aging WDRed drives out of my Qnap before they caused me any trouble. With the pile of drives just sitting there I decided to use them for backups and testing, non important things. I got a LSI Sata/SAS 9260-8i and made a raid6 with 8 drives.

I knew that Windows Server could create an iscsi target, so I build a physical system with win2022 and created the iscsi target and 6TB Lun. so why not.

i7-3770, 32gb RAMddr3, 2.5-ssd-boot

I copied over several VMs offline and….

All was well, until I tried to use it.

My home learning Vmware lab just hates it. Vmware never officially disconnects, but something just stopped communicating.

Any online VMs hosted on this target just lock up and the esxi hosts get weird about it.

I did diskperf -y on Windows to watch the disk activity in task manager and I see the volume humming along at 109MB/s (1 gig network during vMotion) and then it just drops. Interestingly, windows explorer file copy never has any problems. I can copy up 1tb without any issues.

At this point, I just want to build a reliable host, Linux is fine.

​

​

Maybe MSFT iscsi isn’t compatible with esxi 6.7 ?

​

Any thoughts would be appreciated.

Benzer Yazılar

Yorum eklemek için giriş yapmalısınız.

2 Yorumları

  1. >I knew that Windows Server could create an iscsi target, so I build a physical system with win2022 and created the iscsi target and 6TB Lun. so why not.
    >
    >At this point, I just want to build a reliable host, Linux is fine.
    >
    >Maybe MSFT iscsi isn’t compatible with esxi 6.7 ?

    Microsoft’s iSCSI has had serious performance issues since 2016. Haven’t evaluated the 2022 version yet. For your project, I would suggest using Starwind free SAN & NAS. It allows to use HBA controller to create an MDADM or ZFS pool or use hardware RAID and expose the iSCSI LUN to the ESXi. Basically, Starwind is certified for VMware ESXi. https://www.starwindsoftware.com/free-san-and-nas.

  2. So, iSCSI layered with hardware raid is an interesting combination. Not saying it’s impossible but you have several layers of obfuscation going on.

    It could be you’re seeing different caching mechanisms at play, possibly working against you.

    Try turning off all caching on your raid controller, now you have caching from the Windows kernel, and the Unix kernel VMware uses.

    Try your same tests again, use resource monitor in addition to task manager. Keep an eye on memory usage and drive activity percentage (not just throughput.)

    It’s easier to monitor under Linux, where you can see the IOWait percentage, and queue depth for the drive (or array in your case.)