Date: Thu, 18 May 2006 00:19:57 -0700 From: "D X" <dragonx@gmail.com> To: freebsd-geom@freebsd.org Subject: GEOM, gvinum, and SATA disks in standby Message-ID: <1f3e40760605180019w38f724c9uf17d91dd89652147@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
After idling my gvinum RAID1 array using ataidle on a pair of WD Caviar 250GB SATA disks, I almost always get a READ_DMA timeout when trying to access the disk (I'm guessing they take too long to spin up). At this point one of 3 things will happen (which one it is seems random to me at this point) 1. Both disks retry fine, and everything's great. Unfortunately, this happens about 1/3 of the time the disks come out of standby. 2. One of the disks retries fine, but the 2nd disk times out and gets detached. And I have a degraded array. If I try to restart the downed ple= x in gvinum, I get a kernel panic. 3. Both of the disks fail, my OS is partly hung, although I still get responses to ping packets. My console and terminals are dead though, as is my httpd. I usually end up rebooting in this case. I saw a couple of posts online from last year mentioning similar issues. I= s this a known bug that's going to be fixed anytime soon?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1f3e40760605180019w38f724c9uf17d91dd89652147>