From owner-freebsd-fs@FreeBSD.ORG Sat Mar 5 17:01:10 2011 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22D33106564A for ; Sat, 5 Mar 2011 17:01:10 +0000 (UTC) (envelope-from c47g@gmx.at) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by mx1.freebsd.org (Postfix) with SMTP id 041B78FC12 for ; Sat, 5 Mar 2011 17:01:08 +0000 (UTC) Received: (qmail invoked by alias); 05 Mar 2011 16:34:27 -0000 Received: from cm203-32.liwest.at (EHLO bones.gusis.at) [81.10.203.32] by mail.gmx.net (mp028) with SMTP; 05 Mar 2011 17:34:27 +0100 X-Authenticated: #9978462 X-Provags-ID: V01U2FsdGVkX18j1xwoTkcjwwbsTsBk1mu4srChR/Sh/N9JWNgr+A pW+vmogqJvyJY7 From: Christian Gusenbauer To: Kostik Belousov Date: Sat, 5 Mar 2011 17:36:04 +0100 User-Agent: KMail/1.13.5 (FreeBSD/9.0-CURRENT; KDE/4.5.5; i386; ; ) References: <201103050851.38930.c47g@gmx.at> <20110305093640.GL78089@deviant.kiev.zoral.com.ua> In-Reply-To: <20110305093640.GL78089@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_0ZmcNdyTe41Uqef" Message-Id: <201103051736.04605.c47g@gmx.at> X-Y-GMX-Trusted: 0 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: current@freebsd.org, fs@freebsd.org Subject: Re: FS errors during unmount after dump'ing X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Mar 2011 17:01:10 -0000 --Boundary-00=_0ZmcNdyTe41Uqef Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Saturday 05 March 2011 10:36:40 Kostik Belousov wrote: > [Added fs, please remove current on reply]. > > On Sat, Mar 05, 2011 at 08:51:38AM +0100, Christian Gusenbauer wrote: > > Hi! > > > > Once in a week I backup my PC using amanda (which uses dump(8)). > > Subsequently unmounting a filesystem (or during shutdown) I get errors > > like these: > > > > handle_workitem_freeblocks: inode 3579904 block count 384 > > handle_workitem_freeblocks: inode 3579962 block count 384 > > /spare: unmount pending error: blocks 768 files 0 > > softdep_waitidle: Failed to flush worklist for 0xc5be2288 > > softdep_waitidle: Failed to flush worklist for 0xc5be2288 > > softdep_waitidle: Failed to flush worklist for 0xc5be2288 > > softdep_waitidle: Failed to flush worklist for 0xc5be2288 > > softdep_waitidle: Failed to flush worklist for 0xc5be2288 > > softdep_waitidle: Failed to flush worklist for 0xc5be2510 > > softdep_waitidle: Failed to flush worklist for 0xc5be2510 > > /data: unmount pending error: blocks 84 files 0 > > > > Note, I get these messages *only* after dumping filesystems! > > > > Is there anything wrong with my filesystems? > > > > Any clues? > > No clues, you did not provided information even to start looking. > > What version of the OS you are using ? > How do you call dump, in particular, did you specified -L ? > Are there any hung (unkillable) processes after the issue appeared ? > Please show all kernel messages, not only the tail of it. Hi! I'm running current revision 219265. Amanda calls dump like this (ps ax output): 2607 ?? DL 0:00.04 dump 0ubLshf 64 1048576 0 - /dev/label/home (dump) so the -L is specified. There are no hung processes. I attach a compressed dmesg output. It appears to me, that the 'handle_workitem_freeblocks' message is printed during the backup. The other messages are printed during shutdown. Thanks, Christian. --Boundary-00=_0ZmcNdyTe41Uqef--