From owner-freebsd-isp@FreeBSD.ORG Tue Oct 21 16:17:31 2008 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E39F61065676 for ; Tue, 21 Oct 2008 16:17:31 +0000 (UTC) (envelope-from brdbrd@gmail.com) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.178]) by mx1.freebsd.org (Postfix) with ESMTP id 96ED38FC08 for ; Tue, 21 Oct 2008 16:17:31 +0000 (UTC) (envelope-from brdbrd@gmail.com) Received: by el-out-1112.google.com with SMTP id v27so570997ele.13 for ; Tue, 21 Oct 2008 09:17:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=xgXCvxA3sokwbIv0+0dAPEcjR9G/edbelDVqeVl9TIE=; b=EPEVrdNpV7b9tQsoIt06ijHZKpJN3xeiGdRNoZxUbpGl2rNzmEsGqqRvC23UAyq7uR PG7IiMM7WoSDw657k2GDeW2crR55DZWTuce2UjmwR+i4EG1JWEeRbjbHrCTIZJPwXiWv FPUCeY6Ap3FdJsddECz+nc9BTRPTOXUHmh/pM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=BT84DLwcVoPoHoo3Bre/q/ubCUJYxO4JumrM5X/gw2j+nGw1Ee3v57lGM1Nc27er/I HiDLQwtlcnOxDJ8Xp9JtjoepKYNoBnAvOX/hTrSwoWFncweoSfm69J8bdc5nHqu4b3sY z0fpDuwVrgFgiUexUPnUOxazvTkG9jSPLIbvk= Received: by 10.151.39.2 with SMTP id r2mr14618330ybj.108.1224604586408; Tue, 21 Oct 2008 08:56:26 -0700 (PDT) Received: by 10.150.216.20 with HTTP; Tue, 21 Oct 2008 08:56:26 -0700 (PDT) Message-ID: <35ffa5710810210856q34ec73cbhac8d2bd5b58a780@mail.gmail.com> Date: Tue, 21 Oct 2008 09:56:26 -0600 From: "Brad Davis" Sender: brdbrd@gmail.com To: "Troy Settle" In-Reply-To: <48F7852D.2080809@psknet.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <48F7852D.2080809@psknet.com> X-Google-Sender-Auth: ac82516eb9a74ba1 Cc: freebsd-isp@freebsd.org Subject: Re: slow file access X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2008 16:17:32 -0000 On Thu, Oct 16, 2008 at 12:17, Troy Settle wrote: > > All, > > I have a 4-STABLE box that's been in service for 5+ years. Yes, I know it's > old, but it's been rock-solid, and migration to a new server would take days > to accomplish, but I fear that's what I'm faced with.. > > Specs on the server: Dual Xeon 2.8Ghz / 4GB / ~35GB RAID-1 (system) / ~105GB > RAID-5 (mail storage) > > For the last week or so, I've been getting spurts of MySQL connection > failures in my mail logs, but the total number of connections never even > comes close the max connections allowed for the server. > > Occasionally, our website will appear to completely stall for a few seconds, > and most frustrating of all, when I'm poking around in a shell, things will > sometimes hang for several seconds while performing certain tasks (like cd, > ls, tail, etc...). Even top took like 8 seconds to start displaying a > process list. According to raidutil, both raid volumes are optimal. > Nothing shows up in syslog. Here's some info from top(1): > > last pid: 8799; load averages: 0.20, 0.43, 0.38 up 35+23:48:22 > 14:11:46 > 263 processes: 2 running, 261 sleeping > Mem: 1027M Active, 2100M Inact, 393M Wired, 178M Cache, 199M Buf, 75M Free > Swap: 4096M Total, 72K Used, 4096M Free > > I'm at a loss as to what I should look at next... anyone have any > suggestions before I commit myself to a VERY long weekend moving everything > to a new box? I would check to make sure the disks aren't flaking out. Depending on if you can see the individual disks in the RAID you could run smartctl on them to make sure they aren't remapping sectors or something like that. I have seen this manifest from disk problems where the RAID controller still thinks the disks are OK. Regards, Brad Davis