Date: Sun, 18 Jul 2010 23:01:03 -0400 From: Mike Tancsa <mike@sentex.net> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: freebsd-stable@freebsd.org Subject: Re: deadlock or bad disk ? RELENG_8 Message-ID: <201007190301.o6J31Hs1045607@lava.sentex.ca> In-Reply-To: <20100719023419.GA91006@icarus.home.lan> References: <201007182108.o6IL88eG043887@lava.sentex.ca> <20100718211415.GA84127@icarus.home.lan> <201007182142.o6ILgDQW044046@lava.sentex.ca> <20100719023419.GA91006@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
At 10:34 PM 7/18/2010, Jeremy Chadwick wrote: >On Sun, Jul 18, 2010 at 05:42:14PM -0400, Mike Tancsa wrote: > > At 05:14 PM 7/18/2010, Jeremy Chadwick wrote: > > > > >Where exactly is your swap partition? > > > > On one of the areca raidsets. > > > > # swapctl -l > > Device: 1024-blocks Used: > > /dev/da0s1b 10485760 108 > >So is da0 actually a RAID volume "behind the scenes" on the Areca >controller? How many disks are involved in that set? yes, da0 is a RAID volume with 4 disks behind the scenes. >Well, the thread I linked you stated that the problem has to do with a >controller or disk "taking too long". I have no idea what the threshold >is. I suppose it could also indicate that your system is (possibly) >running low on resources (RAM); I would imagine swap_pager would get >called if a processes needed to be offloaded to swap. So maybe this is >a system tuning thing more than a hardware thing. Prior to someone rebooting it, it had been stuck in this state for a good 90min. Apart from upgrading to a later RELENG_8 to get the security patches, the machine had been running a few versions of RELENG_8 doing the same workloads every week without issue. /boot/loader.conf has ahci_load="YES" siis_load="YES" sysctl.conf has net.inet.tcp.recvbuf_max=16777216 net.inet.tcp.recvspace=131072 net.inet.tcp.sendbuf_max=16777216 net.inet.tcp.sendspace=32768 net.inet.udp.recvspace=65536 kern.ipc.somaxconn=1024 kern.ipc.maxsockbuf=4194304 net.inet.ip.redirect=0 net.inet.ip.intr_queue_maxlen=4096 net.route.netisr_maxqlen=1024 kern.ipc.nmbclusters=131072 I do track some basic mem stats via rrd. Looking at the graphs upto that period, nothing unusual was happening CPU: 16.6% user, 0.0% nice, 4.3% system, 0.2% interrupt, 78.8% idle Mem: 443M Active, 5707M Inact, 1462M Wired, 147M Cache, 828M Buf, 166M Free Swap: 10G Total, 124K Used, 10G Free > > smartctl -a -d 3ware,1 /dev/twa0 > >Now I'm confused -- this indicates twa(4) is involved, not arcmsr(4). The other controllers (3ware and onboard ich in ahci mode) provider other storage on the same box. I only noted them in that I checked all their disks for errors of which there were none either. The dmesg from the original post enumerates all the devices on the box. ---Mike -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201007190301.o6J31Hs1045607>