From owner-freebsd-current@FreeBSD.ORG Tue Apr 20 20:09:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 5FE0916A4CE; Tue, 20 Apr 2004 20:09:00 -0700 (PDT) Received: from localhost (green@localhost [127.0.0.1]) by green.homeunix.org (8.12.11/8.12.11) with ESMTP id i3L38wa0045347; Tue, 20 Apr 2004 23:08:59 -0400 (EDT) (envelope-from green@green.homeunix.org) Message-Id: <200404210308.i3L38wa0045347@green.homeunix.org> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: Kris Kennaway In-Reply-To: Message from Kris Kennaway <20040421002916.GA70060@xor.obsecurity.org> From: "Brian F. Feldman" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 20 Apr 2004 23:08:58 -0400 Sender: green@green.homeunix.org cc: Bruce M Simpson cc: current@freebsd.org cc: Daniel Lang cc: mckusick@freebsd.org Subject: Re: A way to recover deleted files (just contents) from USF2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 21 Apr 2004 03:09:00 -0000 Kris Kennaway wrote: > On Tue, Apr 20, 2004 at 07:47:17PM +0100, Bruce M Simpson wrote: > > On Tue, Apr 20, 2004 at 11:57:37AM -0400, Brian F. Feldman wrote: > > > That sounds like a cool idea. Maybe you could write a small program to do > > > that and an rc.d script for it? Simplest operation would be something like: > > [snip] > > > > I second that this also sounds like a cool idea, albeit limited on a > > per-filesystem basis. Snapshotting all filesystems would obviously be > > a bad idea. > > I tried this once but ran into deadlocks with the snap code. These > might have since been fixed. Also, creating the snapshot was > sometimes taking an exceedingly long time, which is bad since it locks > out all filesystem write access while the operation is in progress. Until just a few minutes ago I thought snapshots were perfectly stable :-/ I have never had problems with bgfsck or dump -L but I managed to get: panic("initiate_write_inodeblock_ufs2: already started"); while doing a "make kernel" with bgfsck going on. The coredump lunched so I don't have more info than that. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\