(My comments are at the bottom)
Greg Lehey wrote:
On Monday, 26 June 2006 at 10:41:16 -0400, [EMAIL PROTECTED] wrote:
*** This happens for me using FreeBSD 6.0 or FreeBSD 6.1 with the most
recent MySQL 4.1 or 5.0 built from ports and when the DBMS data files
reside on a NetApp NAS share shared o
The NAS does make snapshots periodically (every few hours), but it
doesn't look like the timestamps of the records match up with when the
backup would have run (the records are written each minute) so I
don't think that that is the cause.
What did you do to resolve the issue?
--
Mark P. Hennes
*** This happens for me using FreeBSD 6.0 or FreeBSD 6.1 with the most
recent MySQL 4.1 or 5.0 built from ports and when the DBMS data files reside on
a NetApp NAS share shared over NFS. It only seems to happen with very
frequently written-to tables. I sent this to the list last week and no
on
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 f
No InnoDB here, just some old ISAM tables.
Sorry about my stupidity on this one, I have only myself to blame...
I have a bunch of old-school ISAM tables that need to be converted to
MyISAM, is there any way to do this en-masse?
(I.E. not having to go through each DB in the DBMS and
ALTER TABLE t
I have a MySQL DBMS running with a mysql DB that apparently is an InnoDB
DB, all other DBs in this DBMS are MyISAM. When I try to upgrade, I get
the following output:
041215 16:41:53 mysqld started
InnoDB: Resetting space id's in the doublewrite buffer
041215 16:41:57 InnoDB: Started; log seque
Is there a way to log authentication failures against the mysqld by
source IP and username attempted?
--
Mark P. Hennessy [EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.m
