:Hello Matthew,
:
:thank you for reviewing vfs_bio.c. Your patch seems to
:solve the problem with NFS writes remaining uncommitted.
:At the time I can't see any NFS related data corruption.
:
:But when shutting down the server it still panics complaining
:about dirty bufs. (happens in 9 out of 10
I've seen this for a non-NFS case.
On Mon, 1 Feb 1999, Matthew Dillon wrote:
:Hello Matthew,
:
:thank you for reviewing vfs_bio.c. Your patch seems to
:solve the problem with NFS writes remaining uncommitted.
:At the time I can't see any NFS related data corruption.
:
:But when
On Fri, Jan 29, 1999 at 01:23:05AM -0800, Matthew Dillon wrote:
[...]
Please try this diff ( against RELENG_3 kern/vfs_bio.c ) and
tell me if it works.
This is for STABLE only. Current already has this patch.
Hello Matthew,
thank you for reviewing vfs_bio.c. Your patch seems
Hello,
as Matthew said in freebsd-current@ vfs_bio:getblk() still
needs work (B_CACHE/B_DELWRI stuff).
Running 3.0-stable (Jan 26) it still happens that some NFS
writes seem to remain uncommited on the server.
Is there a chance to get it into -stable before releasing
in mid February?
Thanks,
:Hello,
:
:as Matthew said in freebsd-current@ vfs_bio:getblk() still
:needs work (B_CACHE/B_DELWRI stuff).
:
:Running 3.0-stable (Jan 26) it still happens that some NFS
:writes seem to remain uncommited on the server.
:
:Is there a chance to get it into -stable before releasing
:in mid February?
:Hello,
:
:as Matthew said in freebsd-current@ vfs_bio:getblk() still
:needs work (B_CACHE/B_DELWRI stuff).
:
:Running 3.0-stable (Jan 26) it still happens that some NFS
:writes seem to remain uncommited on the server.
:
:Is there a chance to get it into -stable before releasing
:in mid February?
