From owner-freebsd-questions@FreeBSD.ORG Sun Aug 10 13:01:20 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 C54FE2DF for ; Sun, 10 Aug 2014 13:01:20 +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 85EB72164 for ; Sun, 10 Aug 2014 13:01:20 +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 BB4E93CC07; Sun, 10 Aug 2014 15:01:18 +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 s7AD1I3l004996; Sun, 10 Aug 2014 15:01:18 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sun, 10 Aug 2014 15:01:18 +0200 From: Polytropon To: Adam Vande More Subject: Re: operation not permitted on entropy file Message-Id: <20140810150118.10951638.freebsd@edvax.de> In-Reply-To: References: <20140810070239.GA80734@home.parts-unknown.org> <20140810103119.GA26958@slackbox.erewhon.home> <20140810124433.da498898.freebsd@edvax.de> <20140810133030.1eb5d617@gumby.homeunix.com> <20140810144202.2eda9b24.freebsd@edvax.de> 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: Sun, 10 Aug 2014 13:01:20 -0000 On Sun, 10 Aug 2014 07:48:07 -0500, Adam Vande More wrote: > On Sun, Aug 10, 2014 at 7:42 AM, Polytropon wrote: > > > (And I also lost files due to "too much automatism", but could > > regain the data; "fsck -yf" isn't always fist choice: "inode > > corrected" - file present, size 0, data gone.) > > > Zero length files after fsck are a side effect of SU, not background > fsck's. Same thing basically happens on EXT4. Yes, I didn't say it had anything to do with background fsck. In fact, it was a "normal" foreground fsck that caused it. But by grep'ing through the disk, 4 hours later I got the data (which I had worked on the whole day) back. :-) The problem that scared me away from background fsck had been the creation of some snapshot, maybe even damaged, that prevented a normal run of foreground fsck, and in the result got me a big data loss. Several years (!) later, I got my data back, like "by accident": removing the snapshot enabled fsck to perform its inteded task normally. It brought back all data and most of the file names and tree structures. See my first posts to this list if you want to read the whole terrible story. ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...