Date: Sat, 9 Jul 2005 08:46:58 +0200 From: "Daniel Eriksson" <daniel_k_eriksson@telia.com> To: <freebsd-current@freebsd.org> Cc: Pawel Jakub Dawidek <pjd@FreeBSD.org> Subject: RE: New ggate broken? Message-ID: <4F9C9299A10AE74E89EA580D14AA10A602858C@royal64.emp.zapto.org>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F9C9299A10AE74E89EA580D14AA10A602858C>