From owner-freebsd-current@FreeBSD.ORG Mon May 31 10:44:10 2010 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9CAC0106566B; Mon, 31 May 2010 10:44:10 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 3D22F8FC14; Mon, 31 May 2010 10:44:09 +0000 (UTC) Received: from [127.0.0.1] (pooker.samsco.org [168.103.85.57]) (authenticated bits=0) by pooker.samsco.org (8.14.3/8.14.3) with ESMTP id o4VAi7Dd056317; Mon, 31 May 2010 04:44:07 -0600 (MDT) (envelope-from scottl@samsco.org) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Scott Long In-Reply-To: Date: Mon, 31 May 2010 04:44:07 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <9EA890DC-CDCF-4E12-BB0E-063153400AB6@samsco.org> References: <20100531002417.R96912@maildrop.int.zabbadoz.net> To: Ivan Voras X-Mailer: Apple Mail (2.1078) X-Spam-Status: No, score=-50.0 required=3.8 tests=ALL_TRUSTED, T_RP_MATCHES_RCVD autolearn=unavailable version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on pooker.samsco.org Cc: freebsd-current@FreeBSD.org Subject: Re: SUJ and "mount" reporting X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2010 10:44:10 -0000 On May 31, 2010, at 3:08 AM, Ivan Voras wrote: > On 05/31/10 02:25, Bjoern A. Zeeb wrote: >> On Mon, 31 May 2010, Ivan Voras wrote: >>=20 >>> Shouldn't SU+J be visible in the output of "mount" somehow? I've = just >>> enabled it on a root file system of a machine and while tunefs and >>> dumpfs report both soft-updates and SUJ are enabled (after reboot), >>> the "mount" command only shows "soft-updates". Alternative question: >>> how to verify is it active on a live file system? >>>=20 >>> (running CURRENT from a few hours ago, kernel&world synced) >>=20 >> As previously stated - this is a hack to do what I think you are >> asking for: >> http://people.freebsd.org/~bz/20100309-03-mount.diff >=20 > Yes, this looks like it... >=20 >> Using tunefs, etc. for now would be better. >=20 > I did use tunefs, as I've said, but I'm concerned what would happen = (if > it can - stale kernel?) if the superblock that tunefs reads from the > disk and the kernel state are different. >=20 MNT_* flags need to be deprecated, and the attributes passed in both = directions as key-value pairs. I don't know if anyone else has thought = about this and what it means for backwards compatibility. Scott