Date: Thu, 29 Jun 2006 09:25:34 -0400 (EDT) From: freebsd-stable-archive@cloud9.net To: freebsd-stable@freebsd.org Subject: Re: FreeBSD 6 and MySQL with DBs on a NAS Message-ID: <Pine.BSF.4.63.0606290919250.73237@earl-grey.cloud9.net>
next in thread | raw e-mail | index | archive | help
I wasn't able to find anyone seeing a similar problem as what I describe. I'm using FreeBSD 6.1, MySQL 5.0.21 built from ports and a NetApp share provided over NFS. Has anyone else ever seen the issue as described in the e-mail below? -- Mark P. Hennessy "Alexey Karagodov" <karagodov@gmail.com> wrote: there was some problems with NFS on FreeBSD 6 ... try to google problem related to NFS or search this mailing list 2006/6/27, freebsd-stable-archive@cloud9.net <freebsd-stable-archive@cloud9.net >: 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 _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to " freebsd-stable-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.63.0606290919250.73237>