From owner-freebsd-current@FreeBSD.ORG Tue Apr 29 07:07:48 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 8DBDC37B401 for ; Tue, 29 Apr 2003 07:07:48 -0700 (PDT) Received: from sauron.fto.de (p15106025.pureserver.info [217.160.140.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99CE343F93 for ; Tue, 29 Apr 2003 07:07:47 -0700 (PDT) (envelope-from hschaefer@fto.de) Received: from localhost (localhost.fto.de [127.0.0.1]) by sauron.fto.de (Postfix) with ESMTP id 20E4425C0F9 for ; Tue, 29 Apr 2003 16:07:47 +0200 (CEST) Received: from sauron.fto.de ([127.0.0.1]) by localhost (sauron [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31377-10 for ; Tue, 29 Apr 2003 16:07:46 +0200 (CEST) Received: from giskard.foundation.hs (p509197A0.dip.t-dialin.net [80.145.151.160]) by sauron.fto.de (Postfix) with ESMTP id 1A63B25C0C2 for ; Tue, 29 Apr 2003 16:07:46 +0200 (CEST) Received: from daneel.foundation.hs (daneel.foundation.hs [192.168.20.2]) by giskard.foundation.hs (8.9.3/8.9.3) with ESMTP id QAA65659 for ; Tue, 29 Apr 2003 16:07:45 +0200 (CEST) (envelope-from hschaefer@fto.de) Date: Tue, 29 Apr 2003 16:07:44 +0200 (CEST) From: Heiko Schaefer X-X-Sender: heiko@daneel.foundation.hs To: freebsd-current@freebsd.org Message-ID: <20030429155751.K20908@daneel.foundation.hs> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at fto.de Subject: gbde data 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: Tue, 29 Apr 2003 14:07:48 -0000 Hi List, after trying gbde with 5.0-REL (and getting lots of spontaneous reboots), i switched to current as of yesterday (world and kernel, of course). now behaviour is much better, but i still seem to get data corruption under some circumstances. my suspicion is that gbde doesn't handle the case very well when the mount is really full (i have a habit of doing "tunefs -m 0" at times). i'm talking about a 60gb mount, which looks like this: /dev/ad2s1d.bde 55045610 55028274 17336 100% /space2 the (unpleasant) effect i see is as follows: i copy some file onto that space, which (according to df) still should fit, say 5mb. the copying works, i get no errors - but the data i get when reading that file is not correct. sometimes the file has the correct size according to "ls -l" but is empty when viewed with 'less'. i consistently get the effect that the (corrupted) file on the gbde mount is more compressible than the original, correct file. i assume that there are a lot of zero-bytes (or other low-entropy fillers) in the corrupted variant. once i even had the effect that reading the corrupted file (making an md5 sum) never terminated (i stopped it after some minutes) for a ~5mb file. that's all i can currently think of reporting. please tell me if i can provide any useful information that is not in this mail. regards, Heiko PS: i also have some performance issues with gbde, about which i'll whine some other time :) it seems to me that the transactions on the disc (the way i use gbde at least) are too small to reach the theoretical speed of the harddrive. -- Free Software. Why put up with inferior code and antisocial corporations? http://www.gnu.org/philosophy/why-free.html