From owner-freebsd-geom@FreeBSD.ORG Thu Aug 2 01:40:10 2012 Return-Path: Delivered-To: freebsd-geom@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9A24C1065670 for ; Thu, 2 Aug 2012 01:40:10 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6A7B58FC0A for ; Thu, 2 Aug 2012 01:40:10 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q721eAdX043030 for ; Thu, 2 Aug 2012 01:40:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q721eATc043029; Thu, 2 Aug 2012 01:40:10 GMT (envelope-from gnats) Date: Thu, 2 Aug 2012 01:40:10 GMT Message-Id: <201208020140.q721eATc043029@freefall.freebsd.org> To: freebsd-geom@FreeBSD.org From: Frank Reppin Cc: Subject: Re: kern/170038: [geom] geom_mirror always starts degraded after reboot X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Frank Reppin List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Aug 2012 01:40:10 -0000 The following reply was made to PR kern/170038; it has been noted by GNATS. From: Frank Reppin To: bug-followup@FreeBSD.org, frankreppin@googlemail.com Cc: Subject: Re: kern/170038: [geom] geom_mirror always starts degraded after reboot Date: Thu, 02 Aug 2012 03:30:13 +0200 Me again here... ... another thing that puzzles me... As long as I had 'journalled softupdates' activated I could see that the reported size of my /var partition [/dev/mirror/gm0s1d] did (quite often) show disconcerting usage values when using: df; du -cs {/var,/tmp,/usr} [means - the shown results of 'df' and 'du' did show different usage values for /var - and only /var in my case - no idea why... and it even didn't somehow sync back after a couple of minutes or after rebooting - the results where 'wrong' all the time]. This came especially apparent at one time where 'df' did show me a _negative_ available space on /var (and I wasn't even close to the reserved space - 144M used out of 53G). A simple reboot (with hopes that the background fsck would fix that) wasn't enough - I had to force fsck the partition in question manually in order to show the correct usage values again... The fsck 'error' reported was (all the time): FREE BLOCK COUNTS(S) WRONG IN SUPERBLK and it only applied to /var (for some unknown reason) - I emphasize this, because I too did some decent IO to /usr at this time (like svn co) but /usr was never affected by this. [/var does provide cyrus/postfix/amavis/spamassassin and the such] However - the gmirror rebuild wasn't triggered all the time after rebooting (as I later noticed - and in contratiction to the topic of this report...) - but quite often... I would assume that 6 out of 10 reboots would trigger a gmirror rebuild in my case. ... last but not least - I've disabled SUJ on all my partitions and I've rebooted (for testcases like this several times) and the 'FREE BLOCK COUNTS(S) WRONG IN SUPERBLK' as well as the gmirror rebuilds vanished... no more trouble here - this is so weird... HTH... cheers, frank\ -- 43rd Law of Computing: Anything that can go wr fortune: Segmentation violation -- Core dumped