On 17-7-2010 15:49, Bob Friesenhahn wrote: > On Sat, 17 Jul 2010, Bruno Sousa wrote: >> Jul 15 12:30:48 storage01 SOURCE: eft, REV: 1.16 >> Jul 15 12:30:48 storage01 EVENT-ID: 859b9d9c-1214-4302-8089-b9447619a2a1 >> Jul 15 12:30:48 storage01 DESC: The command was terminated with a >> non-recovered error condition that may have been caused by a flaw in the >> media or an error in the recorded data. > > This sounds like a hard error to me. I suggest using 'iostat -xe' to > check the hard error counts and check the system log files. If your > storage array was undergoing maintenance and had a cable temporarily > disconnected or controller rebooted, then it is possible that hard > errors could be counted. FMA usually waits until several errors have > been reported over a period of time before reporting a fault. > > Bob Thanks for the tip, i already setup a small cron job to run the iostat -xe command every hour. This sort of messages occured during a system backup, so maybe some components are failing under heavy tasks... Oh well, let's just wait and see if something changes.
Once again , thanks for your time. Bruno -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
