From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 22 23:28:19 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id AE25F16A4CE; Mon, 22 Nov 2004 23:28:18 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.13.1/8.13.1) with ESMTP id iAMNSImV017306; Mon, 22 Nov 2004 18:28:18 -0500 (EST) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.1/8.13.1/Submit) id iAMNSHBn017305; Mon, 22 Nov 2004 18:28:17 -0500 (EST) (envelope-from green) Date: Mon, 22 Nov 2004 18:28:17 -0500 From: Brian Fundakowski Feldman To: David Gilbert Message-ID: <20041122232817.GA1473@green.homeunix.org> References: <16795.43373.413946.559615@canoe.dclg.ca> <419BB453.70205@elischer.org> <16795.46413.508033.379777@canoe.dclg.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16795.46413.508033.379777@canoe.dclg.ca> User-Agent: Mutt/1.5.6i cc: freebsd-hackers@freebsd.org cc: freebsd-stable@freebsd.org cc: Julian Elischer Subject: Re: Snapshot corruption. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 23:28:19 -0000 On Wed, Nov 17, 2004 at 03:32:13PM -0500, David Gilbert wrote: > >>>>> "Julian" == Julian Elischer writes: > > Julian> David Gilbert wrote: > > >> I've got a medium busy server (few thousand mail messages a day, > >> web, webmail, imap, etc) that I can fairly reliably reproduce > >> filesystem corruption by creating multiple snapshots and deleting > >> them. > >> > >> I don't think I'm up to debugging this, but I may be able to > >> provide an exercise platform. > > Julian> can you characterise the corruption? > > Sure. Typically the system will crash with an ffs panic of some > random type. When it comes back, we run non-background fsck's because > manual fsck is sometimes required. > > Corruption varies. Some stuff sometimes pops up in lost+found. Some > stuff can vanish (not 100% positive on that). But most worringly, is > that some files come back corrupted (ie berkley db files that db won't > read). Long strings of NUL bytes? Missing data? Spam (from the same file, or from other files)? -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\