cluster peer creat fail
Dear toasters,I am getting a strange error when trying to create cluster peer on 8.3 systemNo firewall and routing seems to be OK, I can trace route a
View ArticleRe: CentOS 6.7 + cDOT 8.3.1: kernel: scsi: host X channel Y id Z lun4194304...
Are both initiators in the same igroup on NetApp? ïÔÐÒÁ×ÌÅÎÏ Ó iPhone > 12 ÏËÔ. 2015 Ç., × 17:30, Momonth <momonth@gmail.com> ÎÁÐÉÓÁÌ(Á): > > Hi, >
View ArticleRe: CentOS 6.7 + cDOT 8.3.1: kernel: scsi: host X channel Y id Z lun4194304...
Yes, they are, both are logged in. On Oct 13, 2015 07:13, "andrei.borzenkov@ts.fujitsu.com" < andrei.borzenkov@ts.fujitsu.com> wrote: > Are both init
View Articlecluster peer error
Dear toasters,I am getting a strange error when trying to create cluster peer on 8.3 systemNo firewall and routing seems to be OK, I can trace route a
View ArticleRe: cluster peer error
Can you provide more details please? Hard to see what's going on here. Can you do a 'net port show' and 'net int show -role intercluster' and 'net i
View ArticleRe: CentOS 6.7 + cDOT 8.3.1: kernel: scsi: host X channel Y id Z lun4194304...
Funky enough .. I have the 2nd cluster in the other DC, running 8.3.1, with CentOS 6.7 initiator (with default version of HBA drivers, firmwares) that
View ArticleRe: CentOS 6.7 + cDOT 8.3.1: kernel: scsi: host X channel Y id Z lun4194304...
>>>>> "Momonth" == Momonth <momonth@gmail.com> writes: Do you have the ostype set correctly? Same initiators on the CentOS 6.7 working system as on
View ArticleRe: CentOS 6.7 + cDOT 8.3.1: kernel: scsi: host X channel Y id Z lun4194304...
Hi On Tue, Oct 13, 2015 at 6:07 PM, John Stoffel <john@stoffel.org> wrote: >>>>>> "Momonth" == Momonth <momonth@gmail.com> writes: > > Do you have t
View ArticleRe: CentOS 6.7 + cDOT 8.3.1: kernel: scsi: host X channel Y id Z lun4194304...
Momonth> On Tue, Oct 13, 2015 at 6:07 PM, John Stoffel <john@stoffel.org> wrote: >>>>>>> "Momonth" == Momonth <momonth@gmail.com> writes: >> >> Do y
View ArticleRe: CentOS 6.7 + cDOT 8.3.1: kernel: scsi: host X channel Y id Z lun4194304...
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
View ArticleRe: CentOS 6.7 + cDOT 8.3.1: kernel: scsi: host X channel Y id Z lun4194304...
On Wed, Oct 14, 2015 at 5:06 PM, Momonth <momonth@gmail.com> wrote: > > I'm tempted to do that, however if it fixes the issue, then I'm not > able to
View ArticleRe: CentOS 6.7 + cDOT 8.3.1: kernel: scsi: host X channel Y id Z lun4194304...
>>>>> "Momonth" == Momonth <momonth@gmail.com> writes: Momonth> On Wed, Oct 14, 2015 at 5:06 PM, Momonth <momonth@gmail.com> wrote: >> >> I'm tempt
View ArticleRe: CentOS 6.7 + cDOT 8.3.1: kernel: scsi: host X channel Y id Z lun4194304...
ïÔÐÒÁ×ÌÅÎÏ Ó iPhone > 14 ÏËÔ. 2015 Ç., × 18:16, Momonth <momonth@gmail.com> ÎÁÐÉÓÁÌ(Á): > >> On Wed, Oct 14, 2015 at 4:13 PM, John Stoffel <john@sto
View ArticleRe: CentOS 6.7 + cDOT 8.3.1: kernel: scsi: host X channel Y id Z lun4194304...
You mean the CDB dump for a LUN that has no issues? Here it is: # /usr/bin/sg_luns -d -vv /dev/sdm open /dev/sdm with flags=0x802 report luns cd
View ArticleRe: CentOS 6.7 + cDOT 8.3.1: kernel: scsi: host X channel Y id Z lun4194304...
Yes, I think I have to open a ticket at this point .. it's just I have CentOS which is strictly speaking not supported, but I'll give it a try. On We
View ArticleRE: CentOS 6.7 + cDOT 8.3.1: kernel: scsi: host X channel Y id Z lun4194304...
I actually mean - dump for LUN having issues ... --- With best regards Andrei Borzenkov Senior system engineer FTS WEMEAI RUC RU SC TMS FOS FUJITSU
View ArticleRe: CentOS 6.7 + cDOT 8.3.1: kernel: scsi: host X channel Y id Z lun4194304...
There is actually no block device (/dev/sd?) being created for the problematic LUN, I really need to say "the problematic SAN paths" here, as only one
View ArticleRe: CentOS 6.7 + cDOT 8.3.1: kernel: scsi: host X channel Y id Z lun4194304...
One more thing: If I move the LUN from the problematic node ("vol move ..") to an aggregate on the healthy node and then re-discover paths - everythi
View ArticleRE: CentOS 6.7 + cDOT 8.3.1: kernel: scsi: host X channel Y id Z lun4194304...
Is any /dev/sg created for *anything* on this target? You can actually use any device name for REPORT LUNS; and it should always be possible to send c
View ArticleRe: CentOS 6.7 + cDOT 8.3.1: kernel: scsi: host X channel Y id Z lun4194304...
No, there is nothing created for the problematic node, the LUN is only available via the node's partner: # /usr/bin/sg_luns -d -vv /dev/sdb open /dev
View Article