From owner-freebsd-stable@FreeBSD.ORG Tue Jan 28 12:16:02 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5C0C8E33 for ; Tue, 28 Jan 2014 12:16:02 +0000 (UTC) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3EAC3167A for ; Tue, 28 Jan 2014 12:16:01 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1W87aC-0006zV-Sf for freebsd-stable@freebsd.org; Tue, 28 Jan 2014 04:16:00 -0800 Date: Tue, 28 Jan 2014 04:16:00 -0800 (PST) From: Jakub Lach To: freebsd-stable@freebsd.org Message-ID: <1390911360834-5880684.post@n5.nabble.com> Subject: .sujournal strangeness after (?) upgrading to 10-STABLE MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 12:16:02 -0000 Unfortunately, I had my first reboot. Not trusting journal (I've enabled it on all filesystems some time ago) I did full few fscks between reboots in single user mode. Unsurprisingly, there were some inconsistencies in / and /var _but_ checking tunefs -p, actually SU+J was disabled there (on all other filesystems it was still enabled)! I don't know how that happened, previously I just didn't trust SU+J enough and did fsck anyway, I hope that explains inconsistencies. For some time I couldn't enable SU+J again, because of .sujournal actaully present both in / and /var - so there was evidence I really enabled it but somehow it disabled itself? Anyway, using chflags 0 I've removed both journals and after fsck was successful in enabling both journals again by tunefs -j enable (/ after a reboot with "read only fs modified" error). However, that new journals (initial ones were created somewhere on 9-STABLE I think) bear an actual date of enabling them- in difference to the old ones, that have just a start of Unix epoch (1970). Is it intended behaviour? /tmp $ ls -lioF .sujournal 3 -r-------- 1 root wheel schg,sunlnk,nodump,opaque 33554432 1 sty 1970 .su /tmp $ cd /var /var $ ls -lioF .sujournal 4 -r-------- 1 root wheel schg,sunlnk,nodump,opaque 33554432 28 sty 02:06 .su -- View this message in context: http://freebsd.1045724.n5.nabble.com/sujournal-strangeness-after-upgrading-to-10-STABLE-tp5880684.html Sent from the freebsd-stable mailing list archive at Nabble.com.