From owner-freebsd-questions@FreeBSD.ORG Mon Aug 11 14:52:01 2014 Return-Path: Delivered-To: freebsd-questions@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 56E877AF for ; Mon, 11 Aug 2014 14:52:01 +0000 (UTC) Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2C26A243E for ; Mon, 11 Aug 2014 14:52:01 +0000 (UTC) Received: by mail-pd0-f180.google.com with SMTP id v10so9146634pde.39 for ; Mon, 11 Aug 2014 07:52:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=UqpptwlMQrporvh7kQbM7vsIJ6nZuKWl3ALZ6Q2zyHs=; b=H65Nss3B0b7Ag0ms4+a/nM938lhTjEpfBjxuJwJpWo5H71kcQz6EJH/TIT7j/bdgCa EUZSYABLUUhr48bKGeSbeQAp9QMEfcZ2EWl7Yv44xjW64i8xw1TYOiLGxJS+8hoZvlXS sUTHN5BgIGuAxY5PmitV5NufRGxxW1HECfNcx2FtJchZ7bUZsxn3DmlwQFSVezFfqjIv fz+lQ7RJ4BTrNjO7I/EKNH7bZ4iG6ZbungAGjuDALJMPQzrh8ShRos7agKegTbFdz1g+ XsuiCaXfsm4qVPVGXpiAKU2KlTx/VFBbemyYd7YZ8iXm57e0DKGHmPg7/Pd4xITuf3SY ehJw== MIME-Version: 1.0 X-Received: by 10.70.34.16 with SMTP id v16mr1869041pdi.153.1407768720688; Mon, 11 Aug 2014 07:52:00 -0700 (PDT) Received: by 10.70.118.132 with HTTP; Mon, 11 Aug 2014 07:52:00 -0700 (PDT) In-Reply-To: <20140811142707.GA10186@home.parts-unknown.org> References: <20140810070239.GA80734@home.parts-unknown.org> <20140810103119.GA26958@slackbox.erewhon.home> <20140810124433.da498898.freebsd@edvax.de> <20140810224038.GD24036@home.parts-unknown.org> <20140811101822.41851cc7.freebsd@edvax.de> <20140811142707.GA10186@home.parts-unknown.org> Date: Mon, 11 Aug 2014 09:52:00 -0500 Message-ID: Subject: Re: operation not permitted on entropy file From: Adam Vande More To: David Benfell Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18 Cc: Polytropon , FreeBSD Questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Aug 2014 14:52:01 -0000 On Mon, Aug 11, 2014 at 9:27 AM, David Benfell wrote: > > I pretty much followed the default installation. But when fsck was > doing its thing, I saw a lot of unexpected SU+J inconsistencies. So > I'm a little puzzled here: Someone posted that fsck uses journaling > Of course fsck only uses it when journaling is enabled. > (which seems very adventurous for something that shouldn't be needed > often) even when the filesystem doesn't normally. Try fsck'ing a nearly full TB FS on a production box that has had a dirty unmount and you will begin to appreciate the adventure a bit more. > And if I don't have > soft updates by default, then why are they being reported by fsck? > This statement doesn't make sense. Can you post the output you're seeing along with the mount options in play? > > And for reference, I notice that journaling decisions need to be made > *prior* to creating the filesystem. > Journaling decisions can be made basically at anytime the FS isn't mounted or mounted ro using tunefs(1). -- Adam