From owner-freebsd-questions Mon Jan 13 14:32:51 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4311F37B401 for ; Mon, 13 Jan 2003 14:32:50 -0800 (PST) Received: from brainlink.com (mail.brainlink.com [66.228.0.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE85D43E4A for ; Mon, 13 Jan 2003 14:32:49 -0800 (PST) (envelope-from anthonyv@brainlink.com) Received: from [24.189.7.159] (account anthonyv HELO brainlink.com) by brainlink.com (CommuniGate Pro SMTP 3.5.3) with ESMTP id 17833477 for questions@freebsd.org; Mon, 13 Jan 2003 17:32:49 -0500 Message-ID: <3E233E8D.8070701@brainlink.com> Date: Mon, 13 Jan 2003 17:32:45 -0500 From: Anthony Volodkin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20021224 X-Accept-Language: en-us, en MIME-Version: 1.0 To: questions@freebsd.org Subject: strange squid/md issue Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I am running FreeBSD 4.7-STABLE and squid 2.4.STABLE6. In order to avoid squid using my harddisks, I've created a memory filesystem and I've made squid use that md mount as it's swap space. This works fine, however, after several days of operation, squid locks up. I am then not able to kill it in any possible way (not -9, not squid -k shutdown, etc). Top says that squid is in the state 'inode' or 'biord' (the state remains constant, but it may be different each time squid dies). The only way to shutdown squid at this point, is to reboot the machine (i dont like doing this frequently). Finally, I've encountered difficulty manipulating files in the md device when this lockup occurs. I tried deleting some files in one of the squid's cache dirs (rm cache_dir/00/00/* for example) and rm locked up as well. Has anyone else encountered this issue? What steps can I take to debug this? Regards, Anthony Volodkin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message