Hello, today we made some tests with failed drives on a zpool. (SNV60, 2xHBA, 4xJBOD connected through 2 Brocade 2800) On the log we found hundred of the following errors: Sep 16 12:04:23 svrt12 fp: [ID 517869 kern.info] NOTICE: fp(0): PLOGI to 11dca failed state=Timeout, reason=Hardware Error Sep 16 12:04:23 svrt12 fctl: [ID 517869 kern.warning] WARNING: fp(0)::PLOGI to 11dca failed. state=c reason=1. Sep 16 12:04:24 svrt12 fp: [ID 517869 kern.info] NOTICE: fp(1): PLOGI to 11dcc failed state=Timeout, reason=Hardware Error Sep 16 12:04:24 svrt12 fctl: [ID 517869 kern.warning] WARNING: fp(1)::PLOGI to 11dcc failed. state=c reason=1. Sep 16 12:04:43 svrt12 fp: [ID 517869 kern.info] NOTICE: fp(0): PLOGI to 11d01 failed state=Timeout, reason=Hardware Error Sep 16 12:04:43 svrt12 fctl: [ID 517869 kern.warning] WARNING: fp(0)::PLOGI to 11d01 failed. state=c reason=1. Sep 16 12:04:44 svrt12 fp: [ID 517869 kern.info] NOTICE: fp(1): PLOGI to 11dca failed state=Timeout, reason=Hardware Error Sep 16 12:04:44 svrt12 fctl: [ID 517869 kern.warning] WARNING: fp(1)::PLOGI to 11dca failed. state=c reason=1. Sep 16 12:05:04 svrt12 fp: [ID 517869 kern.info] NOTICE: fp(0): PLOGI to 11dd6 failed state=Timeout, reason=Hardware Error Sep 16 12:05:04 svrt12 fctl: [ID 517869 kern.warning] WARNING: fp(0)::PLOGI to 11dd6 failed. state=c reason=1. Sep 16 12:05:04 svrt12 fp: [ID 517869 kern.info] NOTICE: fp(1): PLOGI to 11dd6 failed state=Timeout, reason=Hardware Error Could be related to http://sunsolve.sun.com/search/document.do?assetkey=1-26-57773-1 ?? Gino This message posted from opensolaris.org
Gino, although these messages show some similarity to ones in the Sun Alert you are referring to, it looks like this is unrelated. Sun Alert 57773 describes symptoms of a problem seen in SAN configurations with specific switches (Brocade SilkWorm Switch 12000, 24000, 3250, 3850, 3900) with specific FabOS version (prior to 4.4.0b). Gino ?????:> Hello, > today we made some tests with failed drives on a zpool. > (SNV60, 2xHBA, 4xJBOD connected through 2 Brocade 2800)Your switch model is different, so I believe Sun Alert 57773 is not applicable here. Hth, Victor> On the log we found hundred of the following errors: > > Sep 16 12:04:23 svrt12 fp: [ID 517869 kern.info] NOTICE: fp(0): PLOGI to 11dca failed state=Timeout, reason=Hardware Error > Sep 16 12:04:23 svrt12 fctl: [ID 517869 kern.warning] WARNING: fp(0)::PLOGI to 11dca failed. state=c reason=1. > Sep 16 12:04:24 svrt12 fp: [ID 517869 kern.info] NOTICE: fp(1): PLOGI to 11dcc failed state=Timeout, reason=Hardware Error > Sep 16 12:04:24 svrt12 fctl: [ID 517869 kern.warning] WARNING: fp(1)::PLOGI to 11dcc failed. state=c reason=1. > Sep 16 12:04:43 svrt12 fp: [ID 517869 kern.info] NOTICE: fp(0): PLOGI to 11d01 failed state=Timeout, reason=Hardware Error > Sep 16 12:04:43 svrt12 fctl: [ID 517869 kern.warning] WARNING: fp(0)::PLOGI to 11d01 failed. state=c reason=1. > Sep 16 12:04:44 svrt12 fp: [ID 517869 kern.info] NOTICE: fp(1): PLOGI to 11dca failed state=Timeout, reason=Hardware Error > Sep 16 12:04:44 svrt12 fctl: [ID 517869 kern.warning] WARNING: fp(1)::PLOGI to 11dca failed. state=c reason=1. > Sep 16 12:05:04 svrt12 fp: [ID 517869 kern.info] NOTICE: fp(0): PLOGI to 11dd6 failed state=Timeout, reason=Hardware Error > Sep 16 12:05:04 svrt12 fctl: [ID 517869 kern.warning] WARNING: fp(0)::PLOGI to 11dd6 failed. state=c reason=1. > Sep 16 12:05:04 svrt12 fp: [ID 517869 kern.info] NOTICE: fp(1): PLOGI to 11dd6 failed state=Timeout, reason=Hardware Error > > Could be related to http://sunsolve.sun.com/search/document.do?assetkey=1-26-57773-1 ?? > > Gino > > > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
What lead you to the assumption it''s ONLY those switches? Just because the patch is ONLY for those switches doesn''t mean that the bug is only for them. The reason you only see the patch for 3xxx and newer is because the 2xxx was EOL before the patch was released... FabOS is FabOS, the nature of the issue is not hardware related, it''s software related. 2850 or 3850 makes no difference. This message posted from opensolaris.org
> What lead you to the assumption it''s ONLY those > switches? Just because the patch is ONLY for those > switches doesn''t mean that the bug is only for them. > The reason you only see the patch for 3xxx and newer > is because the 2xxx was EOL before the patch was > released... > > FabOS is FabOS, the nature of the issue is not > hardware related, it''s software related. 2850 or > 3850 makes no difference.I think the same. What other problems can make this errors happens? gino This message posted from opensolaris.org