Отправлено с iPhone
14 окт. 2015 г., в 18:16, Momonth momonth@gmail.com написал(а):
On Wed, Oct 14, 2015 at 4:13 PM, John Stoffel john@stoffel.org wrote:
Funky. sounds like maybe rebooting that node (after doing a failover to the other half of the HA pair) might be one solution here.
I'm tempted to do that, however if it fixes the issue, then I'm not able to debug it any further and don't really understand the root cause.
So if you create new LUNs on that problematic node, they all show up with the high LUN id?
Yes, LUN ID changes, it started with 0, I can verify it with "lun mapping show -fields path,lun-id"
If you convert LUN number in hex it is 0x400000. It actually looks like LUN 0, returned in flat addressing format that for some reason gets misinterpreted by Linux. I'd love to see dump of actual CDB on Linux side.
What version of 8.2 are you running? There are some patches out there and we're running 8.2.3P2 ourselves, but not with many LUNs (FCP or iSCSI) at all.
It's cDOT 8.3.1 _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters