Re: debugging frequent kernel panics on 8.2-RELEASE

On Thursday, August 18, 2011 4:09:35 pm Andriy Gapon wrote: > on 17/08/2011 23:21 Andriy Gapon said the following: > > It seems like everything starts with some kind of a race between terminating > > processes in a jail and termination of the jail itself. This is where the > > details are very thi

Re: panic: spin lock held too long (RELENG_8 from today)

On 8/18/2011 8:37 PM, Chip Camden wrote: >> st> Thanks, Attilio. I've applied the patch and removed the extra debug >> st> options I had added (though keeping debug symbols). I'll let you know if >> st> I experience any more panics. >> >> No panic for 20 hours at this moment, FYI. For my NFS s

Re: panic: spin lock held too long (RELENG_8 from today)

Quoth Mike Tancsa on Friday, 19 August 2011: > On 8/18/2011 8:37 PM, Chip Camden wrote: > > >> st> Thanks, Attilio. I've applied the patch and removed the extra debug > >> st> options I had added (though keeping debug symbols). I'll let you know > >> if > >> st> I experience any more panics. >

Re: debugging frequent kernel panics on 8.2-RELEASE

on 19/08/2011 15:14 John Baldwin said the following: > Yes, it is a bug in kgdb that it only walks allproc and not zombproc. Try > this: The patch worked perfectly well for me, thank you! > Index: kthr.c > === > --- kthr.c(revi

Re: USB/coredump hangs in 8 and 9

on 19/08/2011 00:24 Hans Petter Selasky said the following: > On Thursday 18 August 2011 19:04:10 Andriy Gapon wrote: >> If you can help Hans to figure out what you is wrong with USB subsystem in >> this respect that would help us all. > > Hi, > > usb_busdma.c: /* we use "mtx_owned()" instead o

Re: USB/coredump hangs in 8 and 9

2011/8/12 Andrew Boyer : > Re: panic: bufwrite: buffer is not busy??? (originally on freebsd-net) > Re: debugging frequent kernel panics on 8.2-RELEASE (originally on > freebsd-stable) > Re: System hang in USB umass module while processing panic  (originally on > freebsd-usb) > > Hello Andriy and

bad sector in gmirror HDD

System in question: FreeBSD 8.2-STABLE #3: Thu Mar 3 04:52:04 GMT 2011 After a recent power failure, I'm seeing this in my logs: Aug 19 20:36:34 bast smartd[1575]: Device: /dev/ad2, 2 Currently unreadable (pending) sectors And gmirror reports: # gmirror status NameStatus Components

Re: bad sector in gmirror HDD

On Aug 19, 2011, at 1:50 PM, Dan Langille wrote: > Searching on that error message, I was led to believe that identifying the > bad sector and > running dd to read it would cause the HDD to reallocate that bad block. > > http://smartmontools.sourceforge.net/badblockhowto.html > > However, since

Re: bad sector in gmirror HDD

On Fri, Aug 19, 2011 at 04:50:01PM -0400, Dan Langille wrote: > System in question: FreeBSD 8.2-STABLE #3: Thu Mar 3 04:52:04 GMT 2011 > > After a recent power failure, I'm seeing this in my logs: > > Aug 19 20:36:34 bast smartd[1575]: Device: /dev/ad2, 2 Currently unreadable > (pending) sector

Re: panic: spin lock held too long (RELENG_8 from today)

If nobody complains about it earlier, I'll propose the patch to re@ in 8 hours. Attilio 2011/8/19 Mike Tancsa : > On 8/18/2011 8:37 PM, Chip Camden wrote: > >>> st> Thanks, Attilio.  I've applied the patch and removed the extra debug >>> st> options I had added (though keeping debug symbols).  I'

Re: bad sector in gmirror HDD

On Fri, Aug 19, 2011 at 04:50:01PM -0400, Dan Langille wrote: > System in question: FreeBSD 8.2-STABLE #3: Thu Mar 3 04:52:04 GMT 2011 > > After a recent power failure, I'm seeing this in my logs: > > Aug 19 20:36:34 bast smartd[1575]: Device: /dev/ad2, 2 Currently unreadable > (pending) sector

Re: bad sector in gmirror HDD

On Fri, Aug 19, 2011 at 4:57 PM, Diane Bruce wrote: > On Fri, Aug 19, 2011 at 04:50:01PM -0400, Dan Langille wrote: >> System in question: FreeBSD 8.2-STABLE #3: Thu Mar  3 04:52:04 GMT 2011 >> >> After a recent power failure, I'm seeing this in my logs: >> >> Aug 19 20:36:34 bast smartd[1575]: De

Re: bad sector in gmirror HDD

On Fri, Aug 19, 2011 at 05:51:02PM -0700, Kevin Oberman wrote: > On Fri, Aug 19, 2011 at 4:57 PM, Diane Bruce wrote: > > On Fri, Aug 19, 2011 at 04:50:01PM -0400, Dan Langille wrote: > >> System in question: FreeBSD 8.2-STABLE #3: Thu Mar ?3 04:52:04 GMT 2011 > >> > >> After a recent power failure

Re: bad sector in gmirror HDD

On Aug 19, 2011, at 7:21 PM, Jeremy Chadwick wrote: > On Fri, Aug 19, 2011 at 04:50:01PM -0400, Dan Langille wrote: >> System in question: FreeBSD 8.2-STABLE #3: Thu Mar 3 04:52:04 GMT 2011 >> >> After a recent power failure, I'm seeing this in my logs: >> >> Aug 19 20:36:34 bast smartd[1575]:

Re: panic: spin lock held too long (RELENG_8 from today)

Attilio Rao wrote in : at> If nobody complains about it earlier, I'll propose the patch to re@ in 8 hours. Running fine for 45 hours so far. Please go ahead! -- Hiroki pgp3JVRs7kKa0.pgp Description: PGP signature

Re: bad sector in gmirror HDD

On Fri, Aug 19, 2011 at 09:39:17PM -0400, Dan Langille wrote: > > On Aug 19, 2011, at 7:21 PM, Jeremy Chadwick wrote: > > > On Fri, Aug 19, 2011 at 04:50:01PM -0400, Dan Langille wrote: > >> System in question: FreeBSD 8.2-STABLE #3: Thu Mar 3 04:52:04 GMT 2011 > >> > >> After a recent power fa

Re: bad sector in gmirror HDD

On Fri, 19 Aug 2011, Chuck Swiger wrote: Reading the underlying failing drive with dd will help identify any other questionable sectors. However, your drive temps are too high-- many vendors call out either 50C or 55C as the point where drive reliability becomes significantly degraded. The

Re: bad sector in gmirror HDD

On Aug 20, 2011, at 06:24 , Jeremy Chadwick wrote: > You might also be wondering "that dd command writes 512 bytes of zero to > that LBA; what about the old data that was there, in the case that the > drive remaps the LBA?" If you write zeros at OS level to an LBA, you will end up with zeros at