Lots of logging when using OpeniSCSI

E_Mouws

Member
Jan 29, 2019
13
0
6
Hi,

we're using Proxmox 5.3.5 and connected it over 2 x 10GB to a EMC VNX5300.
we see al LUN's presented by the EMC and the LUNs can be used by VM's running on our proxmox cluster.
But in de syslog of the hosts using the EMC we see a lot of kernel messages recurring approx each 20 seconds:
May 14 09:44:55 (hostname replaced) kernel: [577112.669601] sd 3:0:0:1: alua: supports implicit and explicit TPGS
May 14 09:44:55 (hostname replaced) kernel: [577112.669605] sd 3:0:0:1: alua: device naa.6006016046303300465843db20d5e211 port group 1 rel port 5
May 14 09:44:55 (hostname replaced) kernel: [577112.669772] sd 3:0:0:1: [sdw] Very big device. Trying to use READ CAPACITY(16).
May 14 09:44:55 (hostname replaced) kernel: [577112.670802] sd 3:0:0:2: alua: supports implicit and explicit TPGS
May 14 09:44:55 (hostname replaced) kernel: [577112.670804] sd 3:0:0:2: alua: device naa.60060160463033001afa28a36ed7e211 port group 1 rel port 5
May 14 09:44:55 (hostname replaced) kernel: [577112.671926] sd 3:0:0:3: alua: supports implicit and explicit TPGS
May 14 09:44:55 (hostname replaced) kernel: [577112.671928] sd 3:0:0:3: alua: device naa.60060160a0303300c6aa05778a6be911 port group 1 rel port 5
May 14 09:44:55 (hostname replaced) kernel: [577112.674167] sd 3:0:0:4: alua: supports implicit and explicit TPGS
May 14 09:44:55 (hostname replaced) kernel: [577112.674169] sd 3:0:0:4: alua: device naa.600601604630330082d4bb8695d9e211 port group 1 rel port 5
May 14 09:44:55 (hostname replaced) kernel: [577112.675574] sd 3:0:0:5: alua: supports implicit and explicit TPGS
May 14 09:44:55 (hostname replaced) kernel: [577112.675577] sd 3:0:0:5: alua: device naa.60060160463033009c4ed90d9adde211 port group 1 rel port 5
May 14 09:44:55 (hostname replaced) kernel: [577112.675803] sd 3:0:0:5: [sdaa] Very big device. Trying to use READ CAPACITY(16).
May 14 09:44:55 (hostname replaced) kernel: [577112.677052] sd 3:0:0:6: alua: supports implicit and explicit TPGS
May 14 09:44:55 (hostname replaced) kernel: [577112.677054] sd 3:0:0:6: alua: device naa.6006016046303300ea8c97c6afdde211 port group 1 rel port 5
May 14 09:44:55 (hostname replaced) kernel: [577112.677282] sd 3:0:0:6: [sdab] Very big device. Trying to use READ CAPACITY(16).
May 14 09:44:55 (hostname replaced) kernel: [577112.679628] sd 3:0:0:1: alua: port group 01 state A preferred supports tolUsNA
May 14 09:44:55 (hostname replaced) kernel: [577112.679666] sd 3:0:0:2: alua: port group 01 state N non-preferred supports tolUsNA
May 14 09:44:55 (hostname replaced) kernel: [577112.683633] sd 3:0:0:4: alua: port group 01 state A preferred supports tolUsNA
May 14 09:44:55 (hostname replaced) kernel: [577112.683658] sd 3:0:0:3: alua: port group 01 state A preferred supports tolUsNA
May 14 09:44:55 (hostname replaced) kernel: [577112.687639] sd 3:0:0:5: alua: port group 01 state A preferred supports tolUsNA
May 14 09:44:55 (hostname replaced) kernel: [577112.687681] sd 3:0:0:6: alua: port group 01 state N non-preferred supports tolUsNA

Is this indicating an error or informational, or is it caused by the multipathing-setup and how can we configure it to be more quiet ?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!