Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 17 Mar 2005 20:32:00 GMT
From:      Andrew Korovin <admin@freeside.pp.ru>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   kern/78956: Only one write operation attempted on RAID0 (HPT370) before giving up
Message-ID:  <200503172032.j2HKW0Si041352@www.freebsd.org>
Resent-Message-ID: <200503172040.j2HKe2TZ099023@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         78956
>Category:       kern
>Synopsis:       Only one write operation attempted on RAID0 (HPT370) before giving up
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Mar 17 20:40:02 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Andrew Korovin
>Release:        FreeBSD 5.2.1-p13
>Organization:
FreeSide`s Software, Inc.
>Environment:
FreeBSD freeside.pp.ru 5.3-RELEASE-p5 FreeBSD 5.3-RELEASE-p5 #0: Fri Feb  4 04:28:14 MSK 2005     root@freeside.pp.ru:/usr/obj/usr/src/sys/FreeSide  i386
>Description:
When FreeBSD kernel writes to the RAID array (in my case - HPT370, RAID0, /dev/ar0) looks like it tries only one write operation and, in case of failure, it complains about error (ar0 - broken array). After that it's nearly impossible to recover my RAID array. It would be much better if kernel first retry a write operation at least three or more times and only then give up. Looks like it was so in FreeBSD 5.2.1 but somewhy it has changed in FreeBSD 5.3
>How-To-Repeat:
Sample: ataidle -S 1 2 0 (disk in raid0) or more.
>Fix:
      
>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200503172032.j2HKW0Si041352>