From owner-freebsd-current@FreeBSD.ORG  Sun Apr 13 23:55:44 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 04C3737B401
	for <freebsd-current@freebsd.org>;
	Sun, 13 Apr 2003 23:55:44 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 23AC943FA3
	for <freebsd-current@freebsd.org>;
	Sun, 13 Apr 2003 23:55:43 -0700 (PDT)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h3E6teSA006283;
	Mon, 14 Apr 2003 08:55:41 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: matt <matt@grogged.dyndns.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Sun, 13 Apr 2003 18:09:59 CDT."
             <20030413174853.F57816-100000@grogged.dyndns.org> 
Date: Mon, 14 Apr 2003 08:55:40 +0200
Message-ID: <6282.1050303340@critter.freebsd.dk>
cc: freebsd-current@freebsd.org
Subject: Re: GBDE + md() + ccd() = corruption? 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2003 06:55:44 -0000

In message <20030413174853.F57816-100000@grogged.dyndns.org>, matt writes:

>And now the question, To verify the data I've placed on this rather
>unusual setup, I ran md5 on everything I stuck on it.  Some files seem to
>work fine(about half), and I get consistent output from the md5 utility,
>the other half of the files on the device are very inconsistent.  I can
>run md5 on the same file 5 times in a row and get 5 different output
>strings.  To double check things I ran the inconsistent files against
>known good copies sitting on a plain old ufs partition (with diff), and it
>turns out the files *are* different.
>
>Anyone have any idea what's going on here?  Is some portion of this setup
>corrupting the data?

Hmm, that is very bad.  Can you send me an example of the diff ?

How large are your md(4) devices ?

>Also, when writing to the gbde encrypted filesystem I sporadically get
>messages like:
>
>"ENOMEM 0xc26ced80 on 0xc2648b80(md1.bde)"

This is when we cannot sleeplessly allocate memory in the I/O path.
The request gets retried in that case.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.