Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 16 Apr 2002 14:53:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 16 Apr 2002 14:53:03 -0400 Received: from adsl-63-194-239-202.dsl.lsan03.pacbell.net ([63.194.239.202]:26877 "EHLO mmp-linux.matchmail.com") by vger.kernel.org with ESMTP id ; Tue, 16 Apr 2002 14:53:02 -0400 Date: Tue, 16 Apr 2002 11:55:13 -0700 From: Mike Fedyk To: Wichert Akkerman Cc: linux-kernel@vger.kernel.org Subject: Re: implementing soft-updates Message-ID: <20020416185513.GD23513@matchmail.com> Mail-Followup-To: Wichert Akkerman , linux-kernel@vger.kernel.org In-Reply-To: <20020409184605.A13621@cecm.usp.br.suse.lists.linux.kernel> <20020410092807.GA4015@duron.intern.kubla.de.suse.lists.linux.kernel> <20020408203515.B540@toy.ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 16, 2002 at 12:45:53PM +0200, Wichert Akkerman wrote: > In article <20020408203515.B540@toy.ucw.cz>, > Pavel Machek wrote: > >How do you fix errors you find by such background fsck? > > Theoretically I suppose you could use a writeable snapshot and then switch the > fscked snapshot with the currently mounted fs. > Not if there were writes after the fsck. You could probably do it if there were only reads though. If there were writes it would be based on a corrupted (to whatever extent) filesystem. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/