Bug #17570 | Using encrypted swap/disk on Mac OS X 10.4 may cause innodb table corruption | ||
---|---|---|---|
Submitted: | 20 Feb 2006 10:15 | Modified: | 28 Mar 2006 9:22 |
Reporter: | Not Supplied | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | Ver 14.7 Distrib 4.1.15, for apple-darwi | OS: | MacOS (OS X 10.4.4 and 10.4.5) |
Assigned to: | CPU Architecture: | Any |
[20 Feb 2006 10:15]
Not Supplied
[28 Mar 2006 8:14]
Domas Mituzas
Could not reproduce on: Intel iMac, 10.4.5, with encrypted disk PPC iBook, 10.4.5, with encrypted disk and swap Ran sql-bench against both, for days.
[28 Mar 2006 9:22]
Not Supplied
Sorry to hear (well, in a way) that the problem could not be replicated. Since changing our setup to move /usr/local back to the normal/unencrypted root disk volume and disabling encrypted swap we've not had any problems. After running for a week or so on the iMac, I moved the DB back to the G4 MDD system (where the problems were originally experienced) but kept things on the normal/unencrypted root disk volume and kept encrypted swap disabled. It's been running there ever since, completely problem-free. In addition, after another week or so, I setup the iMac as a slave/replication of the G4 MDD's DB and it's also been problem-free. There are only 2 other factors I can think of: - things were cured by a security update ... but that's not too likely as none coincided with the changes we made and the problems going away - Retrospect backups being performed on the system (including the DB files while the DB was running [yes, of dubious value]), in addition to the encrypted swap and encrypted disks, is the combination that causes the problems ... however, we've always run Retrospect for backups in this way (i.e., even when we we only using an encrypted disk but no encrypted swap) I'm still quite convinced there's a problem somewhere as the issue was portable across 2 very different systems with a complete rebuild of the environment surrounding the DB (i.e., only the data files were moved, the disk was not cloned). The only other thing I could suggest is adding the Retrospect backup into the mix.