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
On Sat, Jul 17, 2010 at 10:49 AM, 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
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
Hi all,
Today i notice that one of the ZFS based servers within my company is
complaining about disk errors, but i would like to know if this a real
physical error or something like a transport error or something.
The server in question runs snv_134 attached to 2 J4400 jbods , and the
head-node ha
