From owner-freebsd-stable@FreeBSD.ORG Tue Jun 27 16:31:25 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5480A16A59B for ; Tue, 27 Jun 2006 16:31:25 +0000 (UTC) (envelope-from freebsd-stable-archive@cloud9.net) Received: from russian-caravan.cloud9.net (russian-caravan.cloud9.net [168.100.1.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02C5843D53 for ; Tue, 27 Jun 2006 16:31:22 +0000 (GMT) (envelope-from freebsd-stable-archive@cloud9.net) Received: from russian-caravan.cloud9.net (localhost [127.0.0.1]) by russian-caravan.cloud9.net (Postfix) with SMTP id 2A054194F5 for ; Tue, 27 Jun 2006 12:31:20 -0400 (EDT) Received: from earl-grey.cloud9.net (earl-grey.cloud9.net [168.100.1.1]) by russian-caravan.cloud9.net (Postfix) with ESMTP id F310319522 for ; Tue, 27 Jun 2006 12:31:19 -0400 (EDT) Date: Tue, 27 Jun 2006 12:31:19 -0400 (EDT) From: freebsd-stable-archive@cloud9.net X-X-Sender: mark@earl-grey.cloud9.net To: freebsd-stable@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-AntiVirus: Checked by Vexira Antivirus v1.5 Subject: FreeBSD 6 and MySQL with DBs on a NAS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jun 2006 16:31:25 -0000 Hi, I was wondering if anyone else had encountered this issue and/or come up with what needs to be done to resolve it: I currently have MySQL 5.0.22 built from ports on a FreeBSD 6.1 machine with the DB data residing on a NetApp share connected via NFS. A strange thing happens often after a few hours or a couple of days, some tables that are very active start to crash for no apparent reason as far as I can tell. Example output from check table tablename: +----------------------------+-------+----------+-------------------------------------------------------------------+ | Table | Op | Msg_type | Msg_text | +----------------------------+-------+----------+-------------------------------------------------------------------+ | dbname.tablename | check | warning | Table is marked as crashed | | dbname.tablename | check | error | Found key at page 18259968 that points to record outside datafile | | dbname.tablename | check | error | Corrupt | +----------------------------+-------+----------+-------------------------------------------------------------------+ Upon moving the DB data to a local drive, the system operates flawlessly and has done so for many weeks, but I really need to keep these data on the networked share. The problem didn't happen when I was using FreeBSD 4.11, it only started after upgrading to FreeBSD 6.0 or 6.1. A poster on a MySQL mailing list suggested perhaps it could be a file locking issue at the OS level and so I post my inquiry here. I've seen this happen on FreeBSD 6.0 and 6.1 with MySQL 4.1.x and MySQL 5.0.x built from ports. Has anyone else seen this and if so has a resolution been found? -- Mark P. Hennessy