From owner-freebsd-stable Wed Jan 30 2: 1:37 2002 Delivered-To: freebsd-stable@freebsd.org Received: from dream.mplik.ru (dream.mplik.ru [195.58.1.132]) by hub.freebsd.org (Postfix) with ESMTP id 6CB7A37B404 for ; Wed, 30 Jan 2002 02:01:26 -0800 (PST) Received: from sight (sight.mplik.ru [195.58.27.104]) by dream.mplik.ru (8.9.3/8.9.1) with ESMTP id PAA64307; Wed, 30 Jan 2002 15:01:13 +0500 (YEKT) Date: Wed, 30 Jan 2002 15:01:11 +0500 From: Sergey Gershtein X-Mailer: The Bat! (v1.53bis) Business Reply-To: Sergey Gershtein Organization: Ural Relcom Ltd X-Priority: 3 (Normal) Message-ID: <791310002584.20020130150111@ur.ru> To: Peter Jeremy Cc: freebsd-stable@FreeBSD.ORG Subject: Re[2]: Strange lock-ups during backup over nfs after adding 1024M RAM In-Reply-To: <20020130073449.B78919@gsmx07.alcatel.com.au> References: <20020126204941.H17540-100000@resnet.uoregon.edu> <1931130530386.20020128130947@ur.ru> <20020130073449.B78919@gsmx07.alcatel.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wednesday, January 30, 2002 Peter Jeremy wrote: PJ> Compile and run a kernel with "options DDB". When it locks up, use PJ> Ctrl-Alt-Esc to enter DDB and try "ps" - this will tell you what PJ> processes are running/blocked. (Read ddb(4) for more details). I did that, started backup and when the lock-up happened entered DDB from console. ps output showed that most processes were in 'inode' state (wmesg title of ps output). There were about a hundred of httpd processes and 2 nfsd in 'inode' state. Another one nfsd process was in 'FFS node' state. When I typed 'c' to go on, switched to another console and tried to log in (it froze after hitting enter) I entered DDB again and ps showed that getty process went into 'inode' state too. Could you tell me what this 'inode' state means and what conclusions can be done from the situation? By the way, the file system that is being backuped has a lot (more than 1,000,000) of small files (less than 1Kb each). They are organized in directory structure of about 1000 files per directory. The lock-up happens while backuping these files over nfs. Does it have anything to do with number of inodes? Does name translation cache somehow get overflowed? How all of this is related to the amount of system RAM (no lock-ups ever happened until we increased the amount of RAM from 1Gb to 1,5Gb). Any suggestions are greatly appreciated! Regards, Sergey Gershtein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message