Re: SATA disk disappears
On Friday 11 January 2013 22:47:03 Warren Block wrote: > On Fri, 11 Jan 2013, Wojciech Puchar wrote: > >>> GEOM_MIRROR: Component ada2 (device home1) broken, skipping. > >>> GEOM_MIRROR: Cannot add disk ada2 to home1 (error=22). > >>> > >>> > >>> started gmirror rebuild and it now works at full speed. > >>> > >>> GEOM_MIRROR: Device home1: rebuilding provider ada2. > >>> > >>> > >>> What kind of hardware failure may it be? smartctl -a /dev/ada2 shows > >>> disk is fine. > >> > >> I had a new WD drive recently that had a write error. Reallocated > >> sector count did not go up, but it quickly failed the SMART self-test, > >> short or long. See smartctl(8) about the -t parameters. > > > > this is WD "green" 3TB > > 1T Red here. The firmware is likely very similar. The same here: brandnew WD 2T green, 9.1 stable, svn rev. 244773, not using GEOM. I had that problem two times within the last two weeks, but the smart self tests can not find any errors/bad sectors. Ciao, Christian. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: kldstat / kernel linker deadlock
On Thursday, November 22, 2012 08:26:17 PM Bryan Drewery wrote: > On 8.3-RELEASE I've hit a deadlock with kldstat. > > I can't provide much information as procstat(1) locks up and I have > already rebooted the servers due to it breaking quite a bit in my setup. > > > # kldstat > > Id Refs AddressSize Name > > load: 0.91 cmd: kldstat 9936 [kernel linker] 51.21r 0.00u 0.00s 0% 768k > > ^C > > load: 0.72 cmd: kldstat 9936 [kernel linker] 225.23r 0.00u 0.00s 0% 704k > > load: 0.72 cmd: kldstat 9936 [kernel linker] 225.39r 0.00u 0.00s 0% 704k > > load: 0.42 cmd: kldstat 9936 [kernel linker] 1837.24r 0.00u 0.00s 0% > > 692k > > Short list of affected processes (74 in all): > > root3685 0.0 0.0 3264 700 ?? D 7:27PM 0:00.00 > > kldstat root 67061 0.0 0.0 3380 892 ?? D 7:27PM > > 0:00.00 /usr/bin/netstat -nrf inet root5579 0.0 0.0 3380 > > 892 ?? D 7:37PM 0:00.00 /usr/bin/netstat -nrf inet root > > 6393 0.0 0.0 3264 704 ?? D 7:32PM 0:00.00 /sbin/kldstat -v > > root 99635 0.0 0.1 3324 1244 13 D+7:52PM 0:00.01 > > procstat -ka > > [... 69 more removed ...] > > I had 2 minutely cron entries that were running kldstat(1)/netstat(1). > > Guessing the kldstat(1) and netstat(1) deadlocked initially. Next time get a dump if at all possible. -- John Baldwin ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: SATA disk disappears
On Sat, 12 Jan 2013, Christian Gusenbauer wrote: On Friday 11 January 2013 22:47:03 Warren Block wrote: On Fri, 11 Jan 2013, Wojciech Puchar wrote: GEOM_MIRROR: Component ada2 (device home1) broken, skipping. GEOM_MIRROR: Cannot add disk ada2 to home1 (error=22). started gmirror rebuild and it now works at full speed. GEOM_MIRROR: Device home1: rebuilding provider ada2. What kind of hardware failure may it be? smartctl -a /dev/ada2 shows disk is fine. I had a new WD drive recently that had a write error. Reallocated sector count did not go up, but it quickly failed the SMART self-test, short or long. See smartctl(8) about the -t parameters. this is WD "green" 3TB 1T Red here. The firmware is likely very similar. The same here: brandnew WD 2T green, 9.1 stable, svn rev. 244773, not using GEOM. I had that problem two times within the last two weeks, but the smart self tests can not find any errors/bad sectors. Hmm. The green drives are supposed to go to sleep for power saving, and then there's a multiple-second delay when they have to spin back up on access. That should not be a problem for gmirror, but maybe it is. sysutils/ataidle can turn on the spindown. Some drives do not accept that command, or claim to accept it but ignore it. Worth a try, though. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: SATA disk disappears
On Sat, 12 Jan 2013, Warren Block wrote: Hmm. The green drives are supposed to go to sleep for power saving, and then there's a multiple-second delay when they have to spin back up on access. That should not be a problem for gmirror, but maybe it is. sysutils/ataidle can turn on the spindown. Some drives do not accept that command, or claim to accept it but ignore it. Worth a try, though. Make that: sysutils/ataidle can turn *off* the spindown. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: SATA disk disappears
On Sat, Jan 12, 2013 at 12:10 PM, Warren Block wrote: > On Sat, 12 Jan 2013, Warren Block wrote: > > Hmm. The green drives are supposed to go to sleep for power saving, and >> then there's a multiple-second delay when they have to spin back up on >> access. That should not be a problem for gmirror, but maybe it is. >> sysutils/ataidle can turn on the spindown. Some drives do not accept that >> command, or claim to accept it but ignore it. Worth a try, though. >> > > Make that: sysutils/ataidle can turn *off* the spindown. > > Maybe just bumping kern.cam.ada.default_timeout to 45 or something might help while still allowing drive to function as designed. -- Adam Vande More ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
