From owner-freebsd-questions@FreeBSD.ORG Mon Aug 11 18:51:17 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 579A9CE6 for ; Mon, 11 Aug 2014 18:51:17 +0000 (UTC) Received: from mail-pd0-x22d.google.com (mail-pd0-x22d.google.com [IPv6:2607:f8b0:400e:c02::22d]) (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 28757241C for ; Mon, 11 Aug 2014 18:51:17 +0000 (UTC) Received: by mail-pd0-f173.google.com with SMTP id w10so11165022pde.4 for ; Mon, 11 Aug 2014 11:51:16 -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=fCE2419k46w7Iegalc4vxlUvP9K+BglYhK2xl1LETnQ=; b=joiyHs2QTBN8Os3+MaFCBB0upy6M+DkxcklkzSdCebYBD/imV2eLZd6QrMqIqeXxQg WWd6hJ1XEnpK9ZR+5/Jd8H5Qgw+fFN1TVP1p3KQpWGsQlBX+h0RlT6346Lyn3qzi57PT 7FHaQztWUf0G3s93woyd3ILgDVwDO6H0893HK7gymqwFnTH+f07FBAbLo97D5eYVVcJ9 05Q3PEE/5GsOiXF6+K7WY/5/XfoVFTeZ9j81kWTSlPsYYKUMABinMLRNmbs7V/vohH5X kLf9S27b3cWJ+dBhQw4XwE12zqPo51GzCUdCseebveS4J8d4mL5XAHriSOOJKmK4sIAQ 8tGg== MIME-Version: 1.0 X-Received: by 10.66.196.65 with SMTP id ik1mr2598702pac.154.1407783076660; Mon, 11 Aug 2014 11:51:16 -0700 (PDT) Received: by 10.70.118.132 with HTTP; Mon, 11 Aug 2014 11:51:16 -0700 (PDT) In-Reply-To: <20140811153535.GA30506@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> <20140811171653.b7c60e58.freebsd@edvax.de> <20140811153535.GA30506@home.parts-unknown.org> Date: Mon, 11 Aug 2014 13:51:16 -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 18:51:17 -0000 On Mon, Aug 11, 2014 at 10:35 AM, David Benfell wrote: > On Mon, Aug 11, 2014 at 05:16:53PM +0200, Polytropon wrote: > > On Mon, 11 Aug 2014 09:52:00 -0500, Adam Vande More wrote: > > > 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. > > > > I prefer appreciating my precious data. :-) > > > On my system, it's a 2TB disk. > It isn't just the size, it's the percentage of it used. > > > > 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? > > Ummm, how could I post this output? In single user, read-only mode, I > don't think it got logged anywhere. I didn't take a picture. But I saw > lots of messages referring to "unexpected SU+J inconsistencies." I > remember the abbreviation sequence because I didn't know what it stood > for (and still don't understand 'soft updates'). > Well there are 1000 different ways but script(1) and mdconfig(1) might be the easiest. > > > > Having _no_ soft updates is probably only true for / when the > > traditional partitioned layout has been chosen in the installer > > (that is, for sysinstall; I don't know bsdinstall's defaults > > from my memory). All other partitions are usually initialized > > with soft updates enabled. > > Okay, this part I'm not remembering. It was FreeBSD 10/stable I was > installing (I made a disk with my notebook). I don't know if it was > sysinstall or bsdinstall. > 10/stable would mandate bsdinstall. > > > > Here's an example (restricted to disks): > > > > % mount > > /dev/ad4s1a on / (ufs, local) > > /dev/ad4s1d on /tmp (ufs, local, soft-updates) > > /dev/ad4s1e on /var (ufs, local, soft-updates) > > /dev/ad4s1f on /usr (ufs, local, soft-updates) > > /dev/ad4s1g on /opt (ufs, local, soft-updates) > > /dev/ad6 on /home (ufs, local, soft-updates) > > > Mine: > > home# mount > /dev/ada0p3 on / (ufs, local, journaled soft-updates) > devfs on /dev (devfs, local, multilabel) > linprocfs on /usr/compat/linux/proc (linprocfs, local) > > I had understood you to say that neither journaling nor soft-updates > were the default for the / partition. I'm not remembering if they were > presented as options in the install or if I selected those options. > (This isn't stuff I ordinarily think much about.) > SU+J is the default for modern FreeBSD install. > > > As you can see, only / doesn't have soft updates enabled. This > > is the choice I made in sysinstall (FreeBSD 8 here) when the > > disk was new. > > If the the installation program presents the options, there's a > possibility I ticked the selection. I don't remember. > It does present an option dialog, but requires user to click into it. Otherwise SU+J will be created. > > > > 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). > > Ah. Okay. I was only looking at the gjournal man page. > gjournal has nothing to do with SU+J. > > > The safest way to change those settings is to enter single user > > mode and use tunefs on the unmounted partitions. > > -- > David Benfell > See https://parts-unknown.org/node/2 if you don't understand the > attachment. > -- Adam