From owner-freebsd-fs@FreeBSD.ORG Mon Nov 20 05:00:20 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 90EA416A412 for ; Mon, 20 Nov 2006 05:00:20 +0000 (UTC) (envelope-from sjr@comcast.net) Received: from alnrmhc12.comcast.net (alnrmhc12.comcast.net [204.127.225.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7908C43D5F for ; Mon, 20 Nov 2006 05:00:06 +0000 (GMT) (envelope-from sjr@comcast.net) Received: from istari.comcast.net (c-68-32-119-244.hsd1.md.comcast.net[68.32.119.244](misconfigured sender)) by comcast.net (alnrmhc12) with ESMTP id <20061120050019b1200mt7g4e>; Mon, 20 Nov 2006 05:00:19 +0000 Received: from istari.comcast.net (localhost [127.0.0.1]) by istari.comcast.net (8.13.8/8.13.8) with ESMTP id kAK50BSs031888; Mon, 20 Nov 2006 00:00:15 -0500 (EST) (envelope-from sjr@istari.comcast.net) Message-Id: <200611200500.kAK50BSs031888@istari.comcast.net> Date: Mon, 20 Nov 2006 00:00:11 -0500 (EST) From: "Stephen J. Roznowski" To: lapo@lapo.it In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Cc: freebsd-fs@freebsd.org Subject: Re: Snapshot corruption on 6.1/amd64 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Nov 2006 05:00:20 -0000 On 13 Nov, Lapo Luchini wrote: > Kostik Belousov gmail.com> writes: > >> > >After some searching, I've found a bug report filed last year that >> > >describes this problem exactly, though the log of that report does >> > >not suggest that anything has been done with it. That report is at >> > >http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/90512 >> >> James, look at the PR/100365. Supposed fix is MFCed. Original reporter >> said that this changed nothing for him. I have not much time lately to >> look at this problem, but would like to get additional data points. As the submitter of 100365, I still don't think that snapshots on amd64 are working correctly. When I (still) run the code attached to the PR, I still see a problem -- the problem is that sometimes the filesystem is busy and mksnap_ffs "errors out" and doesn't create a snapshot. I spent a little bit of time looking at mksnap_ffs to see if I could get it to retry the snapshot if the filesystem is busy to no avail. I've given up on my automated script to do a backup and just generate (and fsck by hand) a snapshot until I get a working one.... Thanks, -SR -- Stephen J. Roznowski (sjr@comcast.net)