Date: Sun, 15 Aug 2004 20:22:12 +0200 From: "Daniel Eriksson" <daniel_k_eriksson@telia.com> To: <freebsd-current@freebsd.org> Cc: 'Nate Lawson' <nate@root.org> Subject: RE: More ATA interrupt(?) oddities Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA0VcX9IoJqUaXPS8MjT1PdsKAAAAQAAAAUbQ9T3z70Umu3YHj9EiyLQEAAAAA@telia.com> In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA0VcX9IoJqUaXPS8MjT1PdsKAAAAQAAAAoNu2Yh496EGUjY%2BelIrSIgEAAAAA@telia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I wrote: > Sometime during the last 3 weeks, something has changed in=20 > the kernel that makes one of my servers barf when hit with > lots of I/O on multiple filesystems (like when starting > "fsck" on all the filesystems). This used to work in the > past, but I have unfortunately not run this stress-test in > the last 3 weeks despite upgrading the kernel multiple times I would like to apologize for shouting "fire" when there is, in fact, nothing burning. After much head-scratching, some emails with S=F6ren = and Nate and trying out a few old kernels without any success, I decided to = replace the PSU powering the discs that were causing the timeout messages = mentioned in my original email. That fixed the problem. I suspect that the = combination of rather unusual temperatures in Sweden over the last 10 days, and very poor ventilation in the room where the server sits, contributed to the "half-death" of the PSU. I should have known better than to suspect FreeBSD given the symptoms = (which I've actually seen once before when I think about it), and I would like = to apologize for any time wasted trying to help me. /Daniel Eriksson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA0VcX9IoJqUaXPS8MjT1PdsKAAAAQAAAAUbQ9T3z70Umu3YHj9EiyLQEAAAAA>