Data corruption over NFS in -current
Stefan Bethke
stb at lassitu.de
Wed Jan 11 18:14:47 UTC 2012
Am 11.01.2012 um 17:57 schrieb Martin Cracauer:
> I'm sorry for the unspecific bug report but I thought a heads-up is
> better than none.
>
> $ uname -a
> FreeBSD wings.cons.org 10.0-CURRENT FreeBSD 10.0-CURRENT #2: Wed Dec
> 28 12:19:21 EST 2011
> cracauer at wings.cons.org:/usr/src/sys/amd64/compile/WINGS amd64
I'm sure Rick will want to know which NFS version, which client code (default new code I'm assuming) and which mount options...
> I see filesystem corruption on NFS filesystems here. I am running a
> heavy shellscript that is noodling around with ascii files assembling
> them with awk and whatnot. Some actions are concurrent with up to 21
> forks doing full-CPU load scripting. This machine is a K8 with a
> total of 8 cores, diskless NFS and memory filesystem for /tmp.
>
> I observe two problems:
> - for no reason whatsoever, some files change from my
> (user/group) cracauer/wheel to root/cracauer
> - the same files will later be corrupted. The beginning of the file
> is normal but then it has what looks like parts of /usr/ports,
> including our CVS files and binary junk, mostly zeros
>
> I did do some ports building lately but not at the same time that this
> problem manifested itself. I speculate some ports blocks were still
> resident in the filesystem buffer cache.
>
> Server is Linux.
>
> Martin
> --
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> Martin Cracauer <cracauer at cons.org> http://www.cons.org/cracauer/
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
--
Stefan Bethke <stb at lassitu.de> Fon +49 151 14070811
More information about the freebsd-current
mailing list