I don't know Linux that well, but I know that HP-UX lets you do most
anything to an open file, including deleting it. The file will continue to
exist as long as it is open by at least one process. If I remember
correctly, this is all about the inode use count vs. the directory entry, or
something like that. The file will actually be safe so long as it is not
closed by the last user.
Those files will go away as soon as they are closed, so the database should
be dumped before shutting down mysqld.
The Infoshop by Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032
860.674.8796 / FAX: 860.674.8341
> -----Original Message-----
> From: Martijn Tonies [mailto:m.tonies@stripped]
> Sent: Wednesday, September 26, 2007 10:07 AM
> To: Ananda Kumar; Baron Schwartz
> Cc: Gary Josack; Daniel Kasak; mysql@stripped
> Subject: Re: Ouch! ibdata files deleted. Why no catastrophe?
> > Hi Baron,
> > If the database is huge, the restoring from mysqldump would
> take lot of
> > time.
> > Is there any other alternative.
> Well, not deleting the InnoDB files would be a good start.
> The files were deleted, what do you expect?? Just continue running and
> hoping no-one finds out?
> Re-creating them sure sounds the safest option to me!
> Martijn Tonies
> Database Workbench - tool for InterBase, Firebird, MySQL,
> NexusDB, Oracle &
> MS SQL Server
> Upscene Productions
> My thoughts:
> Database development questions? Check the forum!
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: