Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Dec 1999 11:39:27 -0800 (PST)
From:      Matthew Dillon <dillon@apollo.backplane.com>
To:        Dan Nelson <dnelson@emsphone.com>
Cc:        freebsd-current@freebsd.org
Subject:   Re: NFS client zeroing out blocks on write?
Message-ID:  <199912101939.LAA60264@apollo.backplane.com>
References:  <19991203112518.A43843@dan.emsphone.com> <199912042051.MAA56920@apollo.backplane.com> <19991205024034.A77822@dan.emsphone.com> <199912061912.LAA71576@apollo.backplane.com> <19991209155512.A5898@dan.emsphone.com> <199912092233.OAA53484@apollo.backplane.com> <19991210113631.A982@dan.emsphone.com>

next in thread | previous in thread | raw e-mail | index | archive | help
    Ok, I've managed to reproduce the NFS zeroing problem that Dan reported.

bfileaa
bfileab
bfileac
bfileaa
bfileab
915136512-915144191(7680) 
bfileac

    It sure doesn't happen very often (each bfile is 1G), but hopefully 
    often enough that I can track down what is going on.

    I'm Ccing -current on this to give everyone an update - plus I think
    a few other certified NFS loons might be interested in attempting to
    help locate the problem too.

    At the moment I am focusing my attention on the nfs_write() code.

    					-Matt



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912101939.LAA60264>