From owner-freebsd-questions@FreeBSD.ORG Wed Jun 29 06:39:18 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 1C5D616A41C for ; Wed, 29 Jun 2005 06:39:18 +0000 (GMT) (envelope-from chad@shire.net) Received: from hobbiton.shire.net (hobbiton.shire.net [166.70.252.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id E529143D58 for ; Wed, 29 Jun 2005 06:39:17 +0000 (GMT) (envelope-from chad@shire.net) Received: from [67.161.222.227] (helo=[192.168.99.68]) by hobbiton.shire.net with esmtpa (Exim 4.51) id 1DnWE6-0007Ce-Dn; Wed, 29 Jun 2005 00:39:15 -0600 Mime-Version: 1.0 (Apple Message framework v730) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Chad Leigh -- Shire.Net LLC Date: Wed, 29 Jun 2005 00:39:13 -0600 To: FreeBSD Question X-Mailer: Apple Mail (2.730) X-SA-Exim-Connect-IP: 67.161.222.227 X-SA-Exim-Mail-From: chad@shire.net X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on hobbiton.shire.net X-Spam-Level: X-Spam-Status: No, score=-0.2 required=5.0 tests=AWL,BAYES_50, GREYLIST_ISWHITE autolearn=disabled version=3.0.3 X-SA-Exim-Version: 4.2 (built Mon May 30 00:43:02 MDT 2005) X-SA-Exim-Scanned: Yes (on hobbiton.shire.net) Cc: Chad Leigh Subject: interesting device full issue on jail host machine X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2005 06:39:18 -0000 pid 80941 (tcsh), uid 5051 inumber 166876 on /local/jails/jail1: filesystem full pid 80941 (tcsh), uid 5051 inumber 166876 on /local/jails/jail1: filesystem full pid 80941 (tcsh), uid 5051 inumber 166876 on /local/jails/jail1: filesystem full pid 80941 (tcsh), uid 5051 inumber 166876 on /local/jails/jail1: filesystem full pid 80941 (tcsh), uid 5051 inumber 166876 on /local/jails/jail1: filesystem full pid 80941 (tcsh), uid 5051 inumber 166876 on /local/jails/jail1: filesystem full pid 80941 (tcsh), uid 5051 inumber 166876 on /local/jails/jail1: filesystem full pid 80941 (tcsh), uid 5051 inumber 166876 on /local/jails/jail1: filesystem full pid 80941 (tcsh), uid 5051 inumber 166876 on /local/jails/jail1: filesystem full pid 80941 (tcsh), uid 5051 inumber 166876 on /local/jails/jail1: filesystem full pid 80941 (tcsh), uid 5051 inumber 166876 on /local/jails/jail1: filesystem full pid 80941 (tcsh), uid 5051 inumber 166876 on /local/jails/jail1: filesystem full pid 80941 (tcsh), uid 5051 inumber 166876 on /local/jails/jail1: filesystem full Ok, I had a billion (several complete system logs worth in one morning) of the above message in my system log of a machine used to host jails. This is on a 5.3-R machine. The file system mentioned, / local/jail/jail1 is a /dev/md -- md(4) type file system used to constrain the user in that specific jail to a certain amount of space and to make it easy to dump that filesystem for backups. I don't know what the user of that jail was doing or when it started happening. Is the "inumber 166876" an inode inside the filesystem? Or what does it refer to? I don't know why it continuously stuck that message thousands of times in the system log but I killed the process with that PID and all was well. My interesting issue is that on ssh login to OTHER JAILS on other / dev/md type filesystems, that had nothing to do with that jail or filesystem, login was prevented as the login process would print a similar message to the one above in the login window over and over and over and would never complete login. /local/jails/jail1: write failed, filesystem is full /local/jails/jail1: write failed, filesystem is full /local/jails/jail1: write failed, filesystem is full /local/jails/jail1: write failed, filesystem is full /local/jails/jail1: write failed, filesystem is full Only when I killed the offending process did it allow the login to continue. However, this seemed to be hit or miss. Sometimes an ssh login to a jail (not the offending jail) would work and sometimes it would do the above. Why would this issue with this one jail file system affect jails that had nothing to do with the full filesystem and what happens at login that would dump these console type messages to the ssh login window? Thanks Chad --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad@shire.net