Andriy Gapon wrote:
> on 30/07/2011 23:47 Alexander Motin said the following:
>> After many experiments I believe that problem is not related to this
>> change. I've managed to reproduce it depending on GEOM modules
>> registration order. After I disabled all GEOM modules and only geom_dev
>> left,
on 30/07/2011 23:47 Alexander Motin said the following:
> Kostik Belousov wrote:
>> On Fri, Jul 29, 2011 at 08:30:28PM +, Alexander Motin wrote:
>>> Author: mav
>>> Date: Fri Jul 29 20:30:28 2011
>>> New Revision: 224496
>>> URL: http://svn.freebsd.org/changeset/base/224496
>>>
>>> Log:
>>> I
Kostik Belousov wrote:
> On Fri, Jul 29, 2011 at 08:30:28PM +, Alexander Motin wrote:
>> Author: mav
>> Date: Fri Jul 29 20:30:28 2011
>> New Revision: 224496
>> URL: http://svn.freebsd.org/changeset/base/224496
>>
>> Log:
>> In some cases failed SATA disks may report their presence, but don'
On Fri, Jul 29, 2011 at 08:30:28PM +, Alexander Motin wrote:
> Author: mav
> Date: Fri Jul 29 20:30:28 2011
> New Revision: 224496
> URL: http://svn.freebsd.org/changeset/base/224496
>
> Log:
> In some cases failed SATA disks may report their presence, but don't
> respond to any commands.
Author: mav
Date: Fri Jul 29 20:30:28 2011
New Revision: 224496
URL: http://svn.freebsd.org/changeset/base/224496
Log:
In some cases failed SATA disks may report their presence, but don't
respond to any commands. I've found that because of multiple command
retries, each of which cause 30s ti