From owner-freebsd-current@FreeBSD.ORG Tue Dec 16 08:48:46 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 347C316A4CE for ; Tue, 16 Dec 2003 08:48:46 -0800 (PST) Received: from seahorse.brainstorminternet.net (13.220.118.66.brainstorminternet.net [66.118.220.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 298E243D2D for ; Tue, 16 Dec 2003 08:48:45 -0800 (PST) (envelope-from cewatts@frontier.net) Received: from [10.0.2.130] (229.193.118.66.brainstorminternet.net [66.118.193.229])67053205CF2; Tue, 16 Dec 2003 09:48:44 -0700 (MST) Date: Tue, 16 Dec 2003 09:49:12 -0700 (MST) From: Charlie Watts X-X-Sender: cewatts@delerium.local To: freebsd-current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: NFS, got bad cookie, and Bonnie++ X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Dec 2003 16:48:46 -0000 When using FreeBSD as a client, bonnie++ over NFS fails. Server software does not appear to matter. Bonnie dies if the server is another FreeBSD machine, localhost, or a Linux-based SNAP appliance. Note that bonnie++ with Linux as a client does *not* fail. backup# bonnie++ -u 0 -s 2 -r 1 Using uid:0, gid:0. Writing a byte at a time...done Writing intelligently...done Rewriting...done Reading a byte at a time...done Reading intelligently...done start 'em...done...done...done...done...done... Create files in sequential order...done. Stat files in sequential order...done. Delete files in sequential order...Bonnie: drastic I/O error (rmdir): Directory not empty Cleaning up test directory after error. And the Bonnie.pid directory is left behind with 8000+ empty files in it. These (and many more) are logged on the client the moment "Delete files in sequential order" is printed by Bonnie: Dec 16 09:34:43 backup kernel: got bad cookie vp 0xc298d920 bp 0xc7723c78 Dec 16 09:34:44 backup kernel: got bad cookie vp 0xc298d920 bp 0xc76964e0 There is a PR that discusses this "got bad cookie" issue: http://www.freebsd.org/cgi/query-pr.cgi?pr=33203 Matt Dillon suggests that the "got bad cookie" messages are informational. Nonetheless, Bonnie++ dies with FreeBSD as a client but not (at least) Linux. Is this a Bonnie++ anomoly? It is hurting our confidence in FreeBSD NFS in a big way. Any insight would be greatly appreciated. -- Charlie Watts cewatts@frontier.net