We recently upgraded our operating system version on an F220, F330 and F540 to 5.1.2R3. After a few days we noticed that we had stopped receiving recovered error messages on our SCSI disks. Following is an example of one such message:
Sun Jan 17 02:19:16 PST [isp_main]: Disk 4a.4(0x4e55d0): READ sector 6200854 recovered error (1 17, 1)
We sent a request to support inquiring about the status of these error messages and have been told that beginning with 5.1.2R3 they are no longer being logged.
It is the case that the occasional and infrequent occurrence of these messages on a very active filer is not an indication of a problem, it is
also our understanding that if these messages start increasing (1 an hour or 10-20 per day) on a specific disk for different blocks, then you
should be paying very close attention to that disk and we would notify support.
This seems to have been the case with several disk failures that we have
experienced on our filers.
An RFE (12820) has been filed at our request to supply a toggle for these messages to enable the customer to selectively include or exclude them from the messages file. We believe messages of this nature can be very helpful although one must understand their significance (or insignificance) when they occur.
We have read some of the discussion concerning these messages on toasters but are not aware of anyone else that has noticed their disappearance and would like to see them made available again. Have I missed them?
Does anyone else have an interest in having the flexibility of including
soft error messages in the log files or is there a general consensus that they are unnecessary. We're trying to get support from other users
for making the toggle available.
One step further, we would like to see a list of all such error messages
potentially logged by the system and what they mean. We have seen such lists on other systems and think that they could be helpful for the filers as well.
Thanks.
Greg Kitch UCLA SEASnet Computing Facility 2567 Boelter Hall Los Angeles, CA 90095
Does anyone else have an interest in having the flexibility of including soft error messages in the log files or is there a general consensus that they are unnecessary. We're trying to get support from other users for making the toggle available.
Yes, I would like to have the toggle as well. In the first place, I would like those messages to remain in the log file (I have not upgraded to 5.1 yet but plan to do so next month). We have prevented disk crashes by monitoring them.
Regards Elena
---------------------------------------------------------------- Elena Samsonova e-mail: E.Samsonova@wxs.nl World Access / Planet Internet phone: +31 33 45 40 417 PO Box 2529, 3800 GB Amersfoort fax: +31 33 45 40 401 The Netherlands ----------------------------------------------------------------
Hi, well this explains why when we upgraded to 3.3 NetApp Cache Appliance code that these soft error messages went away as well.
Maybe this is a undocumented new feature - any comments from NetApp would be useful ??
Colin Johnston SA PSINET UK
On Thu, 18 Feb 1999, Greg Kitch wrote:
We recently upgraded our operating system version on an F220, F330 and F540 to 5.1.2R3. After a few days we noticed that we had stopped receiving recovered error messages on our SCSI disks. Following is an example of one such message:
Sun Jan 17 02:19:16 PST [isp_main]: Disk 4a.4(0x4e55d0): READ sector 6200854 recovered error (1 17, 1)
We sent a request to support inquiring about the status of these error messages and have been told that beginning with 5.1.2R3 they are no longer being logged.
It is the case that the occasional and infrequent occurrence of these messages on a very active filer is not an indication of a problem, it is
also our understanding that if these messages start increasing (1 an hour or 10-20 per day) on a specific disk for different blocks, then you
should be paying very close attention to that disk and we would notify support.
This seems to have been the case with several disk failures that we have
experienced on our filers.
An RFE (12820) has been filed at our request to supply a toggle for these messages to enable the customer to selectively include or exclude them from the messages file. We believe messages of this nature can be very helpful although one must understand their significance (or insignificance) when they occur.
We have read some of the discussion concerning these messages on toasters but are not aware of anyone else that has noticed their disappearance and would like to see them made available again. Have I missed them?
Does anyone else have an interest in having the flexibility of including
soft error messages in the log files or is there a general consensus that they are unnecessary. We're trying to get support from other users
for making the toggle available.
One step further, we would like to see a list of all such error messages
potentially logged by the system and what they mean. We have seen such lists on other systems and think that they could be helpful for the filers as well.
Thanks.
Greg Kitch UCLA SEASnet Computing Facility 2567 Boelter Hall Los Angeles, CA 90095
I, too, would very much like to keep those messages, or have a toggle to make them reappear in my logs. I gauge the health of my system by messages such as these.
-ste
Greg Kitch wrote:
We recently upgraded our operating system version on an F220, F330 and F540 to 5.1.2R3. After a few days we noticed that we had stopped receiving recovered error messages on our SCSI disks. Following is an example of one such message:
Sun Jan 17 02:19:16 PST [isp_main]: Disk 4a.4(0x4e55d0): READ sector 6200854 recovered error (1 17, 1)
-
Colin Johnston -
Elena Samsonova -
Greg Kitch -
Shaun T. Erickson