Hi Bruce, I tried Heikki's solution but it did not work. The databases were there and table names but it could not open the idb files. This must be because of the table definitions are being stored in the shared space (according to the documentation)?
Anyway looks like I will have to dump all data, make the changes and re-import everything. That's a bit of a pain for something that seems so trivial, its going to take quite a lot of time as the data is huge. Oh well :) Thanks for your help. Marvin. -----Original Message----- From: Bruce Dembecki [mailto:[EMAIL PROTECTED] Sent: 26 July 2005 16:24 To: Marvin Wright; mysql@lists.mysql.com Subject: Re: Correct way to use innodb_file_per_table? On Jul 26, 2005, at 3:56 AM, Marvin Wright wrote: > > Regarding the file size issue, we are on a 32-bit system running > redhat AS3, we already have idb files in excess of 21Gb, I'm not sure > what the limit is though if any ? > No, typically a 32 bit file system would have limits like 2G or 4G... at 21G already I doubt you'll have a problem... That said I know little more about Linux than how to spell it, so I'm not the best person to give specific information on that. > Just one thought about the shared space, do you think it would be > possible to back up all the current shared data files along with the > iblog files, change the my.cnf file to use a single ibdata file of 2 > gig, then try to start it up. If it did fail how about reverting the > my.cnf and restoring the original ibdata and iblog files, would it > still work after restoring the original files ? With this I could > test Heikki idea without the pssibility of losing data. > Yes, if you start MySQL without the files (simply moving them to a holding directory) and it doesn't come up or can't find the data after it boots you can always put the files (and your original my.cnf) back and go on from there. At least that's how it's supposed to work :-) Best Regards, Bruce ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com ********************************************************************** -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
