From owner-freebsd-current@FreeBSD.ORG Sat Jul 9 06:47:08 2005 Return-Path: X-Original-To: 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 344E616A41C; Sat, 9 Jul 2005 06:47:08 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: from pne-smtpout1-sn1.fre.skanova.net (pne-smtpout1-sn1.fre.skanova.net [81.228.11.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94D3743D46; Sat, 9 Jul 2005 06:47:07 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: from royal64.emp.zapto.org (195.198.193.104) by pne-smtpout1-sn1.fre.skanova.net (7.2.060.1) id 42B813B000344369; Sat, 9 Jul 2005 08:47:06 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Sat, 9 Jul 2005 08:46:58 +0200 Content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Message-ID: <4F9C9299A10AE74E89EA580D14AA10A602858C@royal64.emp.zapto.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: New ggate broken? Thread-Index: AcWEBChTl+WiDY/bRX2ckqY927pKJQAOhz0gAAS0+SA= From: "Daniel Eriksson" To: Cc: Pawel Jakub Dawidek Subject: RE: New ggate broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 09 Jul 2005 06:47:08 -0000 I wrote: > This breaks ggate for me pretty badly. >=20 > Reading from a ggate device is hosed, it generates bogus data. On the > client I get tons of these: >=20 > bad block -349963294392358026, ino 28874759 > bad block -3509451653830704557, ino 28874759 > bad block -3897387729193514355, ino 28874759 > bad block 3626146008983070931, ino 28874759 > bad block 354768189201479432, ino 28874759 > bad block 6451810762019986516, ino 28874759 > bad block -3206562763347448980, ino 28874759 >=20 > Both server and client are up-to-date. Server is UP, client is SMP. >=20 > I am unfortunately forced to back down to a working version=20 > because the > servers need to be up. However, I should be able to help out with some > testing, just not right away. The broken version was 2005.07.08.22.00.00, the one I backed down to (which I now use, so no hardware malfunction) is 2005.07.05.21.00.00. Also, it looks like writing from the client to the server worked. After I backed down the files I had written were ok. One more interesting datapoint is that the exported device was GBDE encoded (I exported the .bde device on the server). /Daniel Eriksson