From owner-freebsd-questions@FreeBSD.ORG Mon Aug 11 16:39:22 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 5346FF67 for ; Mon, 11 Aug 2014 16:39:22 +0000 (UTC) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DE9DF219C for ; Mon, 11 Aug 2014 16:39:21 +0000 (UTC) Received: from r56.edvax.de (port-92-195-111-1.dynamic.qsc.de [92.195.111.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id ED7B43CC62; Mon, 11 Aug 2014 18:39:12 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id s7BGdCdi004328; Mon, 11 Aug 2014 18:39:12 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Mon, 11 Aug 2014 18:39:12 +0200 From: Polytropon To: David Benfell Subject: Re: operation not permitted on entropy file Message-Id: <20140811183912.ef0f20a6.freebsd@edvax.de> 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> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: 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 16:39:22 -0000 On Mon, 11 Aug 2014 08:35:35 -0700, 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. That will probably take up to 30 minutes for a full fsck run. As if this would matter in comparison to the importance of your data... :-) > > > > 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'). After being done in single user mode, type "exit" to continue booting to multi user mode. Then press Ctrl+Alt+PF2 and login with your user name and password - in text mode. Use the editor of choice to create a capture file, for example % ee /tmp/fsck.txt Then press Alt+F1 to see the virtual console where the output of the booting process has been written to. Press Scroll Lock, then use the arrow keys to scroll up to where fsck wrote its messages. Select the first 25 lines with the left mouse button, switch over to Alt+PF2 (editor) and paste the text with the middle mouse button. Then return to Alt+PF1, scroll down, and capture the next portion of the text, back to Alt+PF2, paste - until you have reached the "exit" command. Now save the file and send the text to the mailing list. Yes, I know, this looks complicated, but it's not that you're doing this 50 times every day, so it should work. > > 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. It was bsdinstall. Only older releases use sysinstall. > Mine: > > home# mount > /dev/ada0p3 on / (ufs, local, journaled soft-updates) So you have a single partition approach, with soft updates, and journaling enabled. Mystery solved. :-) > I had understood you to say that neither journaling nor soft-updates > were the default for the / partition. This probably only applies to the "old fashioned" partitioned approach, where you have different partitions for "functionally different" purposes, like /, /tmp, /var, /usr, /home, /opt, /scratch and whatnot. This is mostly found on MBR-styled systems, but also possible when you use the GPT approach. > 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.) Probably you chose the "use the whole disk" setting. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...