Date: Thu, 6 Nov 2008 23:55:08 GMT From: Andrew <fbsdbugs.20.awinder@spamgourmet.com> To: freebsd-gnats-submit@FreeBSD.org Subject: bin/128654: atacontrol does not preserve rebuild status through reboot Message-ID: <200811062355.mA6Nt8kU081531@www.freebsd.org> Resent-Message-ID: <200811070000.mA700EAx035699@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 128654 >Category: bin >Synopsis: atacontrol does not preserve rebuild status through reboot >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Nov 07 00:00:14 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Andrew >Release: 7.0-RELEASE >Organization: >Environment: FreeBSD asdf 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 10:35:36 UTC 2008 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: When you're rebuilding a RAID1 array with atacontrol and reboot, the rebuild status is not preserved and the disk is marked Ok. This causes inconsistency problems as the driver reads from both disks. >How-To-Repeat: atacontrol create RAID1 ad4 ad6 atacontrol detach ata3 (or another channel that contains a disk in ar0) atacontrol attach ata3 (same as above) atacontrol addspare ar0 ad6 (whichever the dropped disk was) atacontrol rebuild ar0 atacontrol status ar0 # Wait just a minute until status says > 0% reboot # ..... atacontrol status ar0 # ac9: ATA RAID1 status: READY # i.e. the rebuild is _not_ continued after reboot. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200811062355.mA6Nt8kU081531>