Hello again, > > I've had 1.13 running my toture-test here for 38 hours now with no > > trouble. > > i'll stress-test it some more after i get to reboot that machine > physically this evening. mounting the filesystems that used to make some > sense with 1.12 after upgrading to 1.13 apparently hanged the machine > after some short time. hmm, i am now on cvs as of yesterday evening, including all your changes in sys/geom/ up to just now (just looked in cvsweb, nothing newer than what i use there). but i still get corruption of data, judging by checksum testing. again, the corrupted file i see is much more compressible than the uncorrupted original. (potentially this could also be an nfs-issue, as i am copying onto the gbde partition via nfs from a 4.6-rc machine. but i can't really imagine that, never had anything like that in all of my non-gbde freebsd nfs experience. if it is an nfs issue, then it would probably be fbsd-5 specific - is there any such known issue ?!) the partition in question now looks like this: e: 117231392 16 4.2BSD 4096 16384 64 # (Cyl. 0*- 7297*) this time i inited gbde's sectorsize to "4096". last time i reported corruption, gbde's sectorsize was at its default (i presume 512). the corruption then 'felt' just the same. very sporadic - and somewhat non-deterministic from my point of view. regards, HeikoReceived on Wed Apr 30 2003 - 03:24:35 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:05 UTC