toasters

toasters@lists.teaparty.net

13514 discussions

LDAP Integration
by markallen 30 Apr '03

30 Apr '03

Sun has announced they will no longer support nis or nisplus in the future and the upgrade path is to LDAP using the iplanet directory server 5.1 on Solaris 9. I upgraded a test environment that is now serving hosts, netgroups, passwd, group, and autmount tables via LDAP. I have Solaris and AIX clients binding to this server. Data Ontap 6.4 came with ldap support but I haven't had any luck getting it to work. I would like to get hosts, passwd, group, and netgetgroup services from LDAP. Here is a listing of my settings: options ldap ldap.base dc=my,dc=domain,dc=com ldap.enable on ldap.name cn=proxyagent,ou=profile,dc=my,dc=domain,dc=com ldap.passwd ****** ldap.port 389 ldap.servers 1xx.2xx.1xx.xx ldap.servers.preferred 1xx.2xx.1xx.xx cat /etc/nsswitch.conf passwd: ldap files hosts: ldap files group: ldap files netgroup: ldap files Any help would be greatly appreciated. I make added these changes and tested it by pinging a host that is in the ldap database and had no luck. -Mark

1 0

RE: i need help making sense of what happened here
by Daniel Finn 30 Apr '03

30 Apr '03

Interesting. Not slots are empty on these. -----Original Message----- From: Dirk Schmiedt [mailto:Dirk.Schmiedt@munich.netsurf.de] Sent: Tuesday, April 29, 2003 2:47 PM To: Daniel Finn Cc: 'toasters(a)mathworks.com' Subject: Re: i need help making sense of what happened here Daniel Finn wrote: >Today a disk failed, but different from what I'm used to seeing. It appears >now that I look at it that disk 4.19 failed and it took spare disk 4.38 and >began rebuilding on that. What seems strange though is that it kept trying >to read or write to disk 4.19 until I physically pulled the disk out. Why >would this have happened? > Hello Daniel It appears, that the electronic controller of your disk failed. The filer tried to tell the disk "you are broken" and tried to write on the disks label, to make shure wherever this disk will go to ... it will tell any technician by it's raidlabel: I am broken. In your case I also see SES error messages for this shelf. ... let's calculate: Disk 19=16+3 Let me guess ... This is a FC-7/8/9 shelf and the slot 2 is/was empty? The slots 2 AND 3 should be filled both in those old schelves, just in case one of those disks breakes... I think you can ignore the warnings you have seen. They were produced by the disks electronic. Smile & regards Dirk

3 2

rdate and time keeping.
by Gavin Kelman 30 Apr '03

30 Apr '03

We're using rdate to keep our Filer's clock in sync to prevent clock skew errors when compiling things on NFS mounts. There seems to be a bug in OnTap 6.3.1R1. The clock works it's way out of sync, (hence why we use rdate), and we get: Tue Apr 29 15:25:18 BST [Java Thread:notice]: TimeDaemon: Rdate (rfc868) server 'dali.lionbio.co.uk' reports that the time is Tue Apr 29 15:25:21 BST 2003, but the filer thinks the time is Tue Apr 29 15:25:18 BST 2003. This time offset is too large to cause us to modify the time automatically (max allowable skew: 1.000 secs). If the time reported by the time server is correct, set the filer time using the 'date' command. So, to clear this, I set the time by hand using "date". This works fine and we occasionally see: Tue Apr 29 16:04:06 BST [Java Thread:info]: TimeDaemon: Time offset within tolerance [dali.lionbio.co.uk]: actual -0.640 secs, tolerance 1.500 secs, not changing time. And after a time we get the first out-of-sync message. In effect, rdate is doing nothing at all to change the time, as the Max Skew rdate will change over is 1 second, but won't bother changing until it's at least 1.5 seconds out of sync. Surely, this is broken? Cheers, Gavin. -- Gavin Kelman Unix Administrator Email : gavin(a)metahusky.net

5 5

AW: CIFSDispatcher Error
by stefan.holzwarth＠adac.de 30 Apr '03

30 Apr '03

I also see that connection terminations. I think you should decrease the cache time to avoid "too less" communication with the DC. Kind Regards Stefan Holzwarth -----Ursprüngliche Nachricht----- Von: Kumar, Rahul [mailto:rahul.kumar@eds.com] Gesendet: Mittwoch, 30. April 2003 08:08 An: Michael Schipp; toasters(a)mathworks.com Betreff: RE: CIFSDispatcher Error Is there ay way to increase the cache time on filer Shd I enable opslock for cifs shares Rahul -----Original Message----- From: Michael Schipp [mailto:mschipp@asi.com.au] Sent: Wednesday, April 30, 2003 11:35 AM To: Kumar, Rahul; 'toasters(a)mathworks.com' Subject: RE: CIFSDispatcher Error From the NOW site. ------------------------------------------------------------------------ ---- Answered You can expect this from the filer. It is mostly due to idle timeouts between the Filer and it's authenticating DC. I would say it is most like ( by default ) a 15 minute drop after the last need to authenticate ( like a new logon, or new cifs share connect that isn't cached ) Thank you Michael A Schipp ASI Solutions IT LAN/WAN Administrator Phone : 02 9384 8095 Mobile : 0402 907 928 E-Mail : mschipp(a)asi.com.au Visit us at http://www.asi.com.au -----Original Message----- From: Kumar, Rahul [mailto:rahul.kumar@eds.com] Sent: Wednesday, 30 April 2003 2:14 PM To: toasters(a)mathworks.com Subject: CIFSDispatcher Error Fellow Toasters, On one of the F820, running Ontap 6.3.1R1 we are seeing lots of [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated We have reset the machine account in win2k nativemode domain a few times but it doesn't seem to be helping. This error is not being seen on our 3 other filers Regards Rahul **** ASI Solutions Disclaimer **** The material transmitted may contain confidential and/or privileged material and is intended only for the addressee. If you receive this in error, please notify the sender and destroy any copies of the material immediately. ASI will protect your Privacy according to the 10 Privacy Principles outlined under the new Privacy Act, Dec 2001. This email is also subject to copyright. Any use of or reliance upon this material by persons or entities other than the addressee is prohibited. E-mails may be interfered with, may contain computer viruses or other defects. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. **** END OF MESSAGE ****

1 0

RE: CIFSDispatcher Error
by Kumar, Rahul 30 Apr '03

30 Apr '03

Is there ay way to increase the cache time on filer Shd I enable opslock for cifs shares Rahul -----Original Message----- From: Michael Schipp [mailto:mschipp@asi.com.au] Sent: Wednesday, April 30, 2003 11:35 AM To: Kumar, Rahul; 'toasters(a)mathworks.com' Subject: RE: CIFSDispatcher Error From the NOW site. ------------------------------------------------------------------------ ---- Answered You can expect this from the filer. It is mostly due to idle timeouts between the Filer and it's authenticating DC. I would say it is most like ( by default ) a 15 minute drop after the last need to authenticate ( like a new logon, or new cifs share connect that isn't cached ) Thank you Michael A Schipp ASI Solutions IT LAN/WAN Administrator Phone : 02 9384 8095 Mobile : 0402 907 928 E-Mail : mschipp(a)asi.com.au Visit us at http://www.asi.com.au -----Original Message----- From: Kumar, Rahul [mailto:rahul.kumar@eds.com] Sent: Wednesday, 30 April 2003 2:14 PM To: toasters(a)mathworks.com Subject: CIFSDispatcher Error Fellow Toasters, On one of the F820, running Ontap 6.3.1R1 we are seeing lots of [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated We have reset the machine account in win2k nativemode domain a few times but it doesn't seem to be helping. This error is not being seen on our 3 other filers Regards Rahul **** ASI Solutions Disclaimer **** The material transmitted may contain confidential and/or privileged material and is intended only for the addressee. If you receive this in error, please notify the sender and destroy any copies of the material immediately. ASI will protect your Privacy according to the 10 Privacy Principles outlined under the new Privacy Act, Dec 2001. This email is also subject to copyright. Any use of or reliance upon this material by persons or entities other than the addressee is prohibited. E-mails may be interfered with, may contain computer viruses or other defects. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. **** END OF MESSAGE ****

1 0

RE: CIFSDispatcher Error
by Michael Schipp 30 Apr '03

30 Apr '03

From the NOW site. ---------------------------------------------------------------------------- Answered You can expect this from the filer. It is mostly due to idle timeouts between the Filer and it's authenticating DC. I would say it is most like ( by default ) a 15 minute drop after the last need to authenticate ( like a new logon, or new cifs share connect that isn't cached ) Thank you Michael A Schipp ASI Solutions IT LAN/WAN Administrator Phone : 02 9384 8095 Mobile : 0402 907 928 E-Mail : mschipp(a)asi.com.au Visit us at http://www.asi.com.au -----Original Message----- From: Kumar, Rahul [mailto:rahul.kumar@eds.com] Sent: Wednesday, 30 April 2003 2:14 PM To: toasters(a)mathworks.com Subject: CIFSDispatcher Error Fellow Toasters, On one of the F820, running Ontap 6.3.1R1 we are seeing lots of [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated We have reset the machine account in win2k nativemode domain a few times but it doesn't seem to be helping. This error is not being seen on our 3 other filers Regards Rahul **** ASI Solutions Disclaimer **** The material transmitted may contain confidential and/or privileged material and is intended only for the addressee. If you receive this in error, please notify the sender and destroy any copies of the material immediately. ASI will protect your Privacy according to the 10 Privacy Principles outlined under the new Privacy Act, Dec 2001. This email is also subject to copyright. Any use of or reliance upon this material by persons or entities other than the addressee is prohibited. E-mails may be interfered with, may contain computer viruses or other defects. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. **** END OF MESSAGE ****

1 0

CIFSDispatcher Error
by Kumar, Rahul 30 Apr '03

30 Apr '03

Fellow Toasters, On one of the F820, running Ontap 6.3.1R1 we are seeing lots of [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated We have reset the machine account in win2k nativemode domain a few times but it doesn't seem to be helping. This error is not being seen on our 3 other filers Regards Rahul

1 0

i need help making sense of what happened here
by Daniel Finn 29 Apr '03

29 Apr '03

Today a disk failed, but different from what I'm used to seeing. It appears now that I look at it that disk 4.19 failed and it took spare disk 4.38 and began rebuilding on that. What seems strange though is that it kept trying to read or write to disk 4.19 until I physically pulled the disk out. Why would this have happened? na3m-be> sysconfig -v NetApp Release 6.1.2R2: Thu Mar 21 02:30:01 PST 2002 System ID: 0016794273 (na3m-be) slot 0: System Board (NetApp System Board V N4) Tue Apr 29 08:00:00 EDT [kern.uptime.filer:info]: 8:00am up 7 days, 19:27 230387 NFS ops, 537297 CIFS ops, 0 HTTP ops Tue Apr 29 08:56:39 EDT [ispfc_timeout:warning]: 4.19 (0x02000013) (0xfffffc0001778348,0x1c,0/0,4947/0/0,70908/0): command timeout, quiescing drive to allow outstanding I/O to complete. Tue Apr 29 08:56:42 EDT [ispfc_timeout:error]: 4.19 (0x02000013): global device timer timeout, initiating device recovery. Tue Apr 29 08:56:42 EDT [ispfc_timeout:warning]: Resetting device 4.19 (0x02000013) to clear outstanding I/O. Tue Apr 29 08:57:18 EDT [ses_admin:error]: No more valid paths to Enclosure Services in shelf 2 on channel 4. Tue Apr 29 08:57:18 EDT [monitor.shelf.configError:CRITICAL]: Configuration error on disk storage shelf attached to slot 4. Please c heck drive placement. Tue Apr 29 08:57:23 EDT [asup.sent.mail:notice]: System Notification mail sent Tue Apr 29 08:58:00 EDT [monitor.globalStatus.critical:CRITICAL]: Disk shelf configuration error. Tue Apr 29 08:59:38 EDT [scsi.cmd.transportError:error]: Device 4.19: Transport error during execution of command: HA status 0x9: cd b 0x4d. Tue Apr 29 08:59:38 EDT last message repeated 7 times Tue Apr 29 09:00:00 EDT [kern.uptime.filer:info]: 9:00am up 7 days, 20:27 230776 NFS ops, 537297 CIFS ops, 0 HTTP ops Tue Apr 29 09:00:00 EDT [monitor.shelf.configError:CRITICAL]: Configuration error on disk storage shelf attached to slot 4. Please c heck drive placement. Tue Apr 29 09:00:20 EDT [scsi.cmd.underrun:error]: Device 4.19: Received a data underrun: cdb 0x12. Not all the data was received. Possible transmission error. I/O will be retried. Tue Apr 29 09:00:20 EDT [monitor.shelf.configError.ok:CRITICAL]: Configuration error previously reported on disk storage shelf attac hed to slot 4 has been corrected. Tue Apr 29 09:00:21 EDT [ses_admin:error]: No more valid paths to Enclosure Services in shelf 2 on channel 4. Tue Apr 29 09:00:21 EDT [monitor.shelf.configError:CRITICAL]: Configuration error on disk storage shelf attached to slot 4. Please c heck drive placement. Tue Apr 29 09:00:26 EDT [asup.sent.mail:notice]: System Notification mail sent Tue Apr 29 09:01:37 EDT [ispfc_timeout:warning]: 4.19 (0x02000013) (0xfffffc0001773f08,0x1c,0/0,4958/0/4947,72354/5372): command tim eout, quiescing drive to allow outstanding I/O to complete. Tue Apr 29 09:01:40 EDT [ispfc_timeout:error]: 4.19 (0x02000013): global device timer timeout, initiating device recovery. Tue Apr 29 09:01:40 EDT [ispfc_timeout:warning]: Resetting device 4.19 (0x02000013) to clear outstanding I/O. Tue Apr 29 09:02:24 EDT [scsi.cmd.underrun:error]: Device 4.19: Received a data underrun: cdb 0x12. Not all the data was received. Possible transmission error. I/O will be retried. Tue Apr 29 09:02:25 EDT [monitor.shelf.configError.ok:CRITICAL]: Configuration error previously reported on disk storage shelf attac hed to slot 4 has been corrected. Tue Apr 29 09:02:25 EDT [scsi.cmd.checkCondition:error]: Device 4.19: Check Condition: CDB 0x1d: Sense Data not ready - (0x2 - 0x4 0x0 0x2). Tue Apr 29 09:02:25 EDT last message repeated 3 times Tue Apr 29 09:02:25 EDT [ses_admin:error]: Enclosure control failed via 4.19 (shelf 2), searching for alternate path Tue Apr 29 09:02:25 EDT [ses_admin:error]: No more valid paths to Enclosure Services in shelf 2 on channel 4. Tue Apr 29 09:02:25 EDT [monitor.shelf.configError:CRITICAL]: Configuration error on disk storage shelf attached to slot 4. Please c heck drive placement. Tue Apr 29 09:02:26 EDT [asup.sent.mail:notice]: System Notification mail sent Tue Apr 29 09:02:55 EDT [monitor.shelf.configError.ok:CRITICAL]: Configuration error previously reported on disk storage shelf attac hed to slot 4 has been corrected. Tue Apr 29 09:02:56 EDT [scsi.cmd.checkCondition:error]: Device 4.19: Check Condition: CDB 0x1d: Sense Data not ready - (0x2 - 0x4 0x0 0x2). Tue Apr 29 09:02:56 EDT last message repeated 3 times Tue Apr 29 09:02:56 EDT [ses_admin:error]: Enclosure control failed via 4.19 (shelf 2), searching for alternate path Tue Apr 29 09:02:56 EDT [ses_admin:error]: No more valid paths to Enclosure Services in shelf 2 on channel 4. Tue Apr 29 09:02:56 EDT [monitor.shelf.configError:CRITICAL]: Configuration error on disk storage shelf attached to slot 4. Please c heck drive placement. Tue Apr 29 09:02:56 EDT [asup.sent.mail:notice]: System Notification mail sent Tue Apr 29 09:03:12 EDT [monitor.shelf.configError.ok:CRITICAL]: Configuration error previously reported on disk storage shelf attac hed to slot 4 has been corrected. Tue Apr 29 09:03:12 EDT [scsi.cmd.checkCondition:error]: Device 4.19: Check Condition: CDB 0x1d: Sense Data not ready - (0x2 - 0x4 0x0 0x2). Tue Apr 29 09:03:12 EDT last message repeated 3 times Tue Apr 29 09:03:12 EDT [ses_admin:error]: Enclosure control failed via 4.19 (shelf 2), searching for alternate path Tue Apr 29 09:03:12 EDT [ses_admin:error]: No more valid paths to Enclosure Services in shelf 2 on channel 4. Tue Apr 29 09:03:12 EDT [monitor.shelf.configError:CRITICAL]: Configuration error on disk storage shelf attached to slot 4. Please c heck drive placement. Tue Apr 29 09:03:13 EDT [asup.sent.mail:notice]: System Notification mail sent Tue Apr 29 09:03:29 EDT [monitor.shelf.configError.ok:CRITICAL]: Configuration error previously reported on disk storage shelf attac hed to slot 4 has been corrected. Tue Apr 29 09:03:29 EDT [scsi.cmd.checkCondition:error]: Device 4.19: Check Condition: CDB 0x1d: Sense Data not ready - (0x2 - 0x4 0x0 0x2). Tue Apr 29 09:03:29 EDT last message repeated 3 times Tue Apr 29 09:03:29 EDT [ses_admin:error]: Enclosure control failed via 4.19 (shelf 2), searching for alternate path Tue Apr 29 09:03:29 EDT [ses_admin:error]: No more valid paths to Enclosure Services in shelf 2 on channel 4. Tue Apr 29 09:03:29 EDT [monitor.shelf.configError:CRITICAL]: Configuration error on disk storage shelf attached to slot 4. Please c heck drive placement. Tue Apr 29 09:03:29 EDT [asup.sendError.throttled:info]: Too many autosupport messages in too short a time: throttling CONFIGURATION _ERROR!!! mail. Tue Apr 29 09:03:50 EDT [monitor.shelf.configError.ok:CRITICAL]: Configuration error previously reported on disk storage shelf attac hed to slot 4 has been corrected. Tue Apr 29 09:03:50 EDT [scsi.cmd.checkCondition:error]: Device 4.19: Check Condition: CDB 0x1d: Sense Data not ready - (0x2 - 0x4 0x0 0x2). Tue Apr 29 09:03:50 EDT last message repeated 3 times Tue Apr 29 09:03:50 EDT [ses_admin:error]: Enclosure control failed via 4.19 (shelf 2), searching for alternate path Tue Apr 29 09:03:50 EDT [ses_admin:error]: No more valid paths to Enclosure Services in shelf 2 on channel 4. Tue Apr 29 09:03:50 EDT [monitor.shelf.configError:CRITICAL]: Configuration error on disk storage shelf attached to slot 4. Please c heck drive placement. Tue Apr 29 09:03:50 EDT [asup.sendError.throttled:info]: Too many autosupport messages in too short a time: throttling CONFIGURATION _ERROR!!! mail. Tue Apr 29 09:04:06 EDT [monitor.shelf.configError.ok:CRITICAL]: Configuration error previously reported on disk storage shelf attac hed to slot 4 has been corrected. Tue Apr 29 09:04:07 EDT [scsi.cmd.checkCondition:error]: Device 4.19: Check Condition: CDB 0x1d: Sense Data not ready - (0x2 - 0x4 0x0 0x2). Tue Apr 29 09:04:07 EDT last message repeated 3 times Tue Apr 29 09:04:07 EDT [ses_admin:error]: Enclosure control failed via 4.19 (shelf 2), searching for alternate path Tue Apr 29 09:04:07 EDT [ses_admin:error]: No more valid paths to Enclosure Services in shelf 2 on channel 4. Tue Apr 29 09:04:07 EDT [monitor.shelf.configError:CRITICAL]: Configuration error on disk storage shelf attached to slot 4. Please c heck drive placement. Tue Apr 29 09:04:07 EDT [asup.sendError.throttled:info]: Too many autosupport messages in too short a time: throttling CONFIGURATION _ERROR!!! mail. Tue Apr 29 09:04:25 EDT [monitor.shelf.configError.ok:CRITICAL]: Configuration error previously reported on disk storage shelf attac hed to slot 4 has been corrected. Tue Apr 29 09:04:25 EDT [scsi.cmd.checkCondition:error]: Device 4.19: Check Condition: CDB 0x1d: Sense Data not ready - (0x2 - 0x4 0x0 0x2). Tue Apr 29 09:04:25 EDT last message repeated 3 times Tue Apr 29 09:04:25 EDT [ses_admin:error]: Enclosure control failed via 4.19 (shelf 2), searching for alternate path Tue Apr 29 09:04:25 EDT [ses_admin:error]: No more valid paths to Enclosure Services in shelf 2 on channel 4. Tue Apr 29 09:04:25 EDT [monitor.shelf.configError:CRITICAL]: Configuration error on disk storage shelf attached to slot 4. Please c heck drive placement. Tue Apr 29 09:04:25 EDT [asup.sendError.throttled:info]: Too many autosupport messages in too short a time: throttling CONFIGURATION _ERROR!!! mail. Tue Apr 29 09:04:44 EDT [monitor.shelf.configError.ok:CRITICAL]: Configuration error previously reported on disk storage shelf attac hed to slot 4 has been corrected. Tue Apr 29 09:04:44 EDT [scsi.cmd.checkCondition:error]: Device 4.19: Check Condition: CDB 0x1d: Sense Data not ready - (0x2 - 0x4 0x0 0x2). Tue Apr 29 09:04:44 EDT last message repeated 3 times Tue Apr 29 09:04:44 EDT [ses_admin:error]: Enclosure control failed via 4.19 (shelf 2), searching for alternate path Tue Apr 29 09:04:44 EDT [ses_admin:error]: No more valid paths to Enclosure Services in shelf 2 on channel 4. Tue Apr 29 09:04:44 EDT [monitor.shelf.configError:CRITICAL]: Configuration error on disk storage shelf attached to slot 4. Please c heck drive placement. Tue Apr 29 09:04:44 EDT [asup.sendError.throttled:info]: Too many autosupport messages in too short a time: throttling CONFIGURATION _ERROR!!! mail. Tue Apr 29 09:05:00 EDT [scsi.cmd.checkCondition:error]: Device 4.19: Check Condition: CDB 0x28:00cc2f18:0008: Sense Data not ready - (0x2 - 0x4 0x0 0x2). Tue Apr 29 09:05:00 EDT [scsi.cmd.checkCondition:error]: Device 4.19: Check Condition: CDB 0x28:00cc2ff8:0008: Sense Data not ready - (0x2 - 0x4 0x0 0x2). Tue Apr 29 09:05:00 EDT [raid.diskFailed:CRITICAL]: Read on data disk 4.19 in volume vol1, RAID group 1, failed; reverting to degrad ed mode. Tue Apr 29 09:05:00 EDT [raid_admin:CRITICAL]: Label write on 4.19 (S/N LKJ781640000101937T4) failed. Tue Apr 29 09:05:00 EDT [raid_admin:CRITICAL]: Label write on 4.19 (S/N LKJ781640000101937T4) failed. Tue Apr 29 09:05:02 EDT [raid_admin:CRITICAL]: Read on data disk 4.19 in volume vol1, RAID group 1, failed; entered degraded mode. Tue Apr 29 09:05:02 EDT [raid_admin:notice]: One disk is missing from volume vol1, RAID group 1. A "hot spare" disk (4.38) is available and the missing disk will be reconstructed on the spare disk. Tue Apr 29 09:05:02 EDT [dyn_dev_qual_admin:info]: Successfully updated /etc/.broken_disks file on local FS for disk 4.19 SEAGATE S T118202FC LKJ781640000101937T4 Tue Apr 29 09:05:02 EDT [asup.sent.mail:notice]: System Notification mail sent Tue Apr 29 09:05:03 EDT [monitor.shelf.configError.ok:CRITICAL]: Configuration error previously reported on disk storage shelf attac hed to slot 4 has been corrected. Tue Apr 29 09:05:03 EDT [scsi.cmd.checkCondition:error]: Device 4.19: Check Condition: CDB 0x1d: Sense Data not ready - (0x2 - 0x4 0x0 0x2). Tue Apr 29 09:05:03 EDT last message repeated 3 times ^ The following continued to be reported to the log file until I physically pulled the drive and replaced it with a spare. The log file continues below: Tue Apr 29 10:12:54 EDT [ispfc_timeout:warning]: Resetting Fibre Channel adapter 4. Tue Apr 29 10:13:00 EDT [scsi.cmd.selectionTimeout:error]: Device 4.19: Adapter/target error: HA status 0x7: cdb 0x12. Targeted dev ice did not respond to requested I/O. I/O will be retried. Tue Apr 29 10:13:00 EDT [scsi.cmd.noMorePaths:error]: Device 4.19: No more paths to device: cdb 0x12. All retries have failed. Tue Apr 29 10:13:17 EDT [ispfc_timeout:warning]: 4.19 (0x02000013) (0xfffffc0001779998,0x12,0/0,1/0/0,98110/0): command timeout, qui escing drive to allow outstanding I/O to complete. Tue Apr 29 10:13:27 EDT [monitor.shelf.configError.ok:CRITICAL]: Configuration error previously reported on disk storage shelf attac hed to slot 4 has been corrected. Tue Apr 29 10:13:30 EDT [dyn_dev_qual_admin:info]: Now downloading firmware file /etc/disk_fw/ST118202FC.NA27.LOD on 1 disk ... Tue Apr 29 10:14:00 EDT [monitor.globalStatus.nonCritical:warning]: Disk on adapter 4, shelf 2, bay 3, failed. Tue Apr 29 10:15:00 EDT [dyn_dev_qual_admin:info]: Firmware downloaded on disk 4.19 Tue Apr 29 10:15:00 EDT [dyn_dev_qual_admin:info]: Media Access test successful on disk 4.19 Tue Apr 29 10:15:00 EDT [dyn_dev_qual_admin:info]: Firmware is up-to-date on all disk drives Tue Apr 29 10:15:00 EDT [raid_disk_admin:notice]: Disk 4.19 (S/N LKH21431000020030EDP) has been added to incomplete volume vol1(1). Tue Apr 29 10:15:00 EDT [monitor.globalStatus.ok:info]: The system's global status is normal. Tue Apr 29 11:00:00 EDT [kern.uptime.filer:info]: 11:00am up 7 days, 22:27 233428 NFS ops, 537525 CIFS ops, 0 HTTP ops Tue Apr 29 11:23:21 EDT [consumer:notice]: Reconstruction of data disk in volume vol1, RAID group 1, complete. Tue Apr 29 11:23:21 EDT [download.update:info]: Begin bootblock update, prototype is 4.8 Tue Apr 29 11:23:29 EDT [download.updateDone:info]: Bootblock update completed Thanks Dan

2 1

Re: 2 telnet sessions
by Dirk Schmiedt 26 Apr '03

26 Apr '03

Sorry, if you get this email twice. My provider T-Online changed their policy of sending emails with a non-t-online from: field in april 2003. They told me the emails would be delivered, but ... :-( So here's the mail again: Dirk Schmiedt wrote: > Jeff Burton wrote: > >> If you are on Unix you can use the below very simple script to simulate >> a command line from as many machines as you want. > > .... > Simple but neat. :-) > >> Until you are comfortable with this script I would NEVER run "dangerous" >> commands like 'halt', 'ifconig e0 down', ... It should work fine, but >> use at your own risk. >> > 100% confirmation. > > rsh filer license > >> license not found. Type '?' for a list of commands > > > Try: > > rsh filer "priv set -q advanced ; license " > > If someone don't know about this "advanced" mode., then you should not > use it. Go to the advanced ONTAP NetApp training first, please. > If you know about the semantic content, you might like this > suggestion. :-) > > Smile & regards > Dirk >

1 0

ISCSI
by Steven Boyer GD mail deployed 26 Apr '03

26 Apr '03

Anybody using ISCSI if so in what capacity, and what kind of I/O are you seeing. I am particularly interested in ISCSI to tape libraries. Thanks Steven

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters