From owner-freebsd-current@FreeBSD.ORG Sun Apr 13 16:20:07 2003 Return-Path: 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 72A0137B401 for ; Sun, 13 Apr 2003 16:20:07 -0700 (PDT) Received: from grogged.dyndns.org (c-66-41-101-53.mn.client2.attbi.com [66.41.101.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id E534A43F3F for ; Sun, 13 Apr 2003 16:20:06 -0700 (PDT) (envelope-from matt@grogged.dyndns.org) Received: by grogged.dyndns.org (Postfix, from userid 1001) id 1AA0B16809; Sun, 13 Apr 2003 18:09:59 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by grogged.dyndns.org (Postfix) with ESMTP id 13EC4D239 for ; Sun, 13 Apr 2003 18:09:59 -0500 (CDT) Date: Sun, 13 Apr 2003 18:09:59 -0500 (CDT) From: matt To: Message-ID: <20030413174853.F57816-100000@grogged.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Apr 2003 23:20:07 -0000 Quick question (please CC me, as I'm not on the list yet) - I have 4x files setup through the md device (md1, md2, md3, mde4), each of which I have init'd and attached gbde to (successfully), for md1.bde, md2.bde, etc... I've used ccdconfig to make these 4 encrypted devices a concatenated disk (ccd0c), where upon I newfs'd /dev/ccd0c and successfully mounted it. 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? Also, when writing to the gbde encrypted filesystem I sporadically get messages like: "ENOMEM 0xc26ced80 on 0xc2648b80(md1.bde)" These messages don't pop up consistently, the hex addresses are always different, and "md1.bde" can often be replaced with any of the other md*.bde devices setup in the config I described. It doesn't seem to matter if I mount the filesystem (ccd0c) read-only, the md5sums are still inconsistent. I've experienced the same problem in a clean install of 5.0-R as well as -current as of a couple days ago. I've replicated this problem on more than one machine with known-to-be-good disks. Comments? Suggestions? Thanks everyone, - Matt