[Lustre-discuss] bad write checksums
Craig Prescott
prescott at hpc.ufl.edu
Fri Jul 24 07:33:32 PDT 2009
Hi;
We've been testing some 1.8.0.1 patchless clients (RHEL5.3, x86_64, RPMs
from the Sun download page) with out 1.6.4.2 servers.
The OSS nodes started logging these LustreErrors from the 1.8.0.1 clients:
> LustreError: 7302:0:(ost_handler.c:1157:ost_brw_write()) client csum 8448447f, original server csum 66fb7cff, server csum now 66fb7cff
> LustreError: 7302:0:(ost_handler.c:1157:ost_brw_write()) Skipped 1 previous similar message
> LustreError: 7391:0:(ost_handler.c:1095:ost_brw_write()) client csum 9d8c7d6a, server csum 2cfdcb47
> LustreError: 168-f: ufhpc-OST0004: BAD WRITE CHECKSUM: changed in transit before arrival at OST from 12345-10.13.28.55 at tcp inum 38470778/1485322248 object 67094039/0 extent [0-1023]
Is this a known issue with running 1.8.0.1 clients against 1.6.4.2
servers? We aren't seeing these messages in relation to our 1.6 clients.
Looking through the Lustre bugzilla, I see bug 18296, which discusses
these messages, but it was logged against Lustre version 1.6.6.
Cheers,
Craig
More information about the lustre-discuss
mailing list