New ggate broken?

[Pawel Jakub Dawidek]

On Sat, Jul 09, 2005 at 08:46:58AM +0200, Daniel Eriksson wrote:
+> > This breaks ggate for me pretty badly.
+> > 
+> > Reading from a ggate device is hosed, it generates bogus data. On the
+> > client I get tons of these:
+> > 
+> > 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
+> > 
+> > Both server and client are up-to-date. Server is UP, client is SMP.
+> > 
+> > I am unfortunately forced to back down to a working version 
+> > 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).

I am not able to reproduce it.
Both machines are i386?

-- 
Pawel Jakub Dawidek                       http://www.wheel.pl
pjd at FreeBSD.org                           http://www.FreeBSD.org
FreeBSD committer                         Am I Evil? Yes, I Am!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20050709/87a0bfc7/attachment.bin