Mark, any chance that a process on the NAS is accessing your data files
for some reason? Backups?
We had some severe crashing problems with MySQL years ago we eventually
traced to a backup process accessing the live data directory.
Dan
[EMAIL PROTECTED] wrote:
*** This happens for me
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.
(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
Good point, should have included in my post. We were already using
mysqlhotcopy to make snapshots of our data in another directory, which
were then subsequently backed up to tape by the backup agent. We set
the backup agent to specifically exclude the live data directory,
*** 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 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 over NFS. It only seems to happen with
very
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
