Re: 1 file
On Wed, Jul 3, 2013 at 9:51 AM, shawn green shawn.l.gr...@oracle.com wrote: Hello Larry, On 7/3/2013 11:27 AM, Larry Martell wrote: We recently changed from in memory files to InnoDB files. Today we noticed that in every server's data dir there is file called '1' that seems to get updated every time the iddata1 file gets updated. On some servers it's comparable in size to the iddata1 file, on other servers it's 10-15x larger, and on others it's 1/2 the size. What is this file. Googling revealed nothing about this. That is not something an official MySQL build would do. Consult with the person (or group) that compiled your binaries. Now, if you have enabled --innodb-file-per-table and if you have named your table '1' then that file is probably '1.ibd'. That would be expected. But that seems unlikely based on your other details. Did you also enable a separate undo log, perhaps? Although if you had, it should be 'undo1' not just '1' http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_undo_tablespaces So, that simple '1' file also seems unusual to me. Thanks for the reply. I asked our DBA group and here's the answer I got: The file is currently accessed by mysqld, please don’t delete it. Looking at the file header, it appeared to be an innodb datafile. But no idea how it was created. Sigh. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: 1 file
Hello Larry, On 7/3/2013 11:27 AM, Larry Martell wrote: We recently changed from in memory files to InnoDB files. Today we noticed that in every server's data dir there is file called '1' that seems to get updated every time the iddata1 file gets updated. On some servers it's comparable in size to the iddata1 file, on other servers it's 10-15x larger, and on others it's 1/2 the size. What is this file. Googling revealed nothing about this. That is not something an official MySQL build would do. Consult with the person (or group) that compiled your binaries. Now, if you have enabled --innodb-file-per-table and if you have named your table '1' then that file is probably '1.ibd'. That would be expected. But that seems unlikely based on your other details. Did you also enable a separate undo log, perhaps? Although if you had, it should be 'undo1' not just '1' http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_undo_tablespaces So, that simple '1' file also seems unusual to me. -- Shawn Green MySQL Principal Technical Support Engineer Oracle USA, Inc. - Hardware and Software, Engineered to Work Together. Office: Blountville, TN -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: 1 file
On Wed, Jul 3, 2013 at 12:36 PM, Rick James rja...@yahoo-inc.com wrote: I once found a slowlog called simply 1. But I did not track down the cause. Possibly it was a not-so-correct configuration script. SHOW VARIABLES LIKE '%dir%'; Nothing was set to 1 ibdata1 grows (never shrinks) when data is added, ALTER is done, etc. It will reuse free space within itself. innodb_file_per_table=1 is recommended Having an explicit PRIMARY KEY on InnoDB tables is recommended. (MEMORY did not care much.) -Original Message- From: Larry Martell [mailto:larry.mart...@gmail.com] Sent: Wednesday, July 03, 2013 9:29 AM To: shawn green Cc: mysql@lists.mysql.com Subject: Re: 1 file On Wed, Jul 3, 2013 at 9:51 AM, shawn green shawn.l.gr...@oracle.com wrote: Hello Larry, On 7/3/2013 11:27 AM, Larry Martell wrote: We recently changed from in memory files to InnoDB files. Today we noticed that in every server's data dir there is file called '1' that seems to get updated every time the iddata1 file gets updated. On some servers it's comparable in size to the iddata1 file, on other servers it's 10-15x larger, and on others it's 1/2 the size. What is this file. Googling revealed nothing about this. That is not something an official MySQL build would do. Consult with the person (or group) that compiled your binaries. Now, if you have enabled --innodb-file-per-table and if you have named your table '1' then that file is probably '1.ibd'. That would be expected. But that seems unlikely based on your other details. Did you also enable a separate undo log, perhaps? Although if you had, it should be 'undo1' not just '1' http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_i nnodb_undo_tablespaces So, that simple '1' file also seems unusual to me. Thanks for the reply. I asked our DBA group and here's the answer I got: The file is currently accessed by mysqld, please don’t delete it. Looking at the file header, it appeared to be an innodb datafile. But no idea how it was created. Sigh. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: 1 file
I once found a slowlog called simply 1. But I did not track down the cause. Possibly it was a not-so-correct configuration script. SHOW VARIABLES LIKE '%dir%'; ibdata1 grows (never shrinks) when data is added, ALTER is done, etc. It will reuse free space within itself. innodb_file_per_table=1 is recommended Having an explicit PRIMARY KEY on InnoDB tables is recommended. (MEMORY did not care much.) -Original Message- From: Larry Martell [mailto:larry.mart...@gmail.com] Sent: Wednesday, July 03, 2013 9:29 AM To: shawn green Cc: mysql@lists.mysql.com Subject: Re: 1 file On Wed, Jul 3, 2013 at 9:51 AM, shawn green shawn.l.gr...@oracle.com wrote: Hello Larry, On 7/3/2013 11:27 AM, Larry Martell wrote: We recently changed from in memory files to InnoDB files. Today we noticed that in every server's data dir there is file called '1' that seems to get updated every time the iddata1 file gets updated. On some servers it's comparable in size to the iddata1 file, on other servers it's 10-15x larger, and on others it's 1/2 the size. What is this file. Googling revealed nothing about this. That is not something an official MySQL build would do. Consult with the person (or group) that compiled your binaries. Now, if you have enabled --innodb-file-per-table and if you have named your table '1' then that file is probably '1.ibd'. That would be expected. But that seems unlikely based on your other details. Did you also enable a separate undo log, perhaps? Although if you had, it should be 'undo1' not just '1' http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_i nnodb_undo_tablespaces So, that simple '1' file also seems unusual to me. Thanks for the reply. I asked our DBA group and here's the answer I got: The file is currently accessed by mysqld, please don’t delete it. Looking at the file header, it appeared to be an innodb datafile. But no idea how it was created. Sigh. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: 1 file
-Original Message- From: Larry Martell [mailto:larry.mart...@gmail.com] Sent: Wednesday, July 03, 2013 11:29 AM To: shawn green Cc: mysql@lists.mysql.com Subject: Re: 1 file On Wed, Jul 3, 2013 at 9:51 AM, shawn green shawn.l.gr...@oracle.com wrote: Hello Larry, On 7/3/2013 11:27 AM, Larry Martell wrote: We recently changed from in memory files to InnoDB files. Today we noticed that in every server's data dir there is file called '1' that seems to get updated every time the iddata1 file gets updated. On some servers it's comparable in size to the iddata1 file, on other servers it's 10-15x larger, and on others it's 1/2 the size. What is this file. Googling revealed nothing about this. That is not something an official MySQL build would do. Consult with the person (or group) that compiled your binaries. Now, if you have enabled --innodb-file-per-table and if you have named your table '1' then that file is probably '1.ibd'. That would be expected. But that seems unlikely based on your other details. Did you also enable a separate undo log, perhaps? Although if you had, it should be 'undo1' not just '1' http://dev.mysql.com/doc/refman/5.6/en/innodb- parameters.html#sysvar_innodb_undo_tablespaces So, that simple '1' file also seems unusual to me. Thanks for the reply. I asked our DBA group and here's the answer I got: The file is currently accessed by mysqld, please don’t delete it. Looking at the file header, it appeared to be an innodb datafile. But no idea how it was created. Sigh. -- I believe this is due to one of the variables in your my.cnf file. You probably set it to 1, thinking this enabled it, but in actuality, the variable can be set by just putting it the my.cnf file If it has an assignment, then the assignment is the file name to use. I think there are several variables that this is the case for For example, log and log_error If you have log_error=1 or log=1 this would be the file There may be others variables, but one of those is where I have seen the 1 file being created before If it isn't one of those two (which it may not, since you said the header looks to be innodb), I would review all the variables that are set to =1, and see if that is the proper assignment MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
Re: 1 file
On Wed, Jul 3, 2013 at 11:34 AM, Peterson, Timothy R timothy_r_peter...@uhc.com wrote: -Original Message- From: Larry Martell [mailto:larry.mart...@gmail.com] Sent: Wednesday, July 03, 2013 11:29 AM To: shawn green Cc: mysql@lists.mysql.com Subject: Re: 1 file On Wed, Jul 3, 2013 at 9:51 AM, shawn green shawn.l.gr...@oracle.com wrote: Hello Larry, On 7/3/2013 11:27 AM, Larry Martell wrote: We recently changed from in memory files to InnoDB files. Today we noticed that in every server's data dir there is file called '1' that seems to get updated every time the iddata1 file gets updated. On some servers it's comparable in size to the iddata1 file, on other servers it's 10-15x larger, and on others it's 1/2 the size. What is this file. Googling revealed nothing about this. That is not something an official MySQL build would do. Consult with the person (or group) that compiled your binaries. Now, if you have enabled --innodb-file-per-table and if you have named your table '1' then that file is probably '1.ibd'. That would be expected. But that seems unlikely based on your other details. Did you also enable a separate undo log, perhaps? Although if you had, it should be 'undo1' not just '1' http://dev.mysql.com/doc/refman/5.6/en/innodb- parameters.html#sysvar_innodb_undo_tablespaces So, that simple '1' file also seems unusual to me. Thanks for the reply. I asked our DBA group and here's the answer I got: The file is currently accessed by mysqld, please don’t delete it. Looking at the file header, it appeared to be an innodb datafile. But no idea how it was created. Sigh. -- I believe this is due to one of the variables in your my.cnf file. You probably set it to 1, thinking this enabled it, but in actuality, the variable can be set by just putting it the my.cnf file If it has an assignment, then the assignment is the file name to use. I think there are several variables that this is the case for For example, log and log_error If you have log_error=1 or log=1 this would be the file There may be others variables, but one of those is where I have seen the 1 file being created before If it isn't one of those two (which it may not, since you said the header looks to be innodb), I didn't say that - one of my DBA's said that. I didn't have permission to look at the file. But one of my sysadmins did and she found that it was ascii text. I would review all the variables that are set to =1, and see if that is the proper assignment I did that and I found it: log-slow-queries = 1 mysql show variables like 'slow_query_log_file'; +-+---+ | Variable_name | Value | +-+---+ | slow_query_log_file | 1 | +-+---+ 1 row in set (0.00 sec) Thanks! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
