hi guys,
i would like to run a mysql-instance on a solaris8-box, using a NASLite-FS for storing all the data- and log-files.
Guess what: it doesn't work. Here some lines of the logfile:
->
16 11:33:55 mysqld started
InnoDB: Unable to lock ./ibdata1, error: 46
050816 11:33:56 InnoDB: Retrying to lock the first data file
InnoDB: Unable to lock ./ibdata1, error: 46
InnoDB: Unable to lock ./ibdata1, error: 46
InnoDB: Unable to lock ./ibdata1, error: 46
InnoDB: Unable to lock ./ibdata1, error: 46
InnoDB: Unable to lock ./ibdata1, error: 46
InnoDB: Unable to lock ./ibdata1, error: 46
InnoDB: Unable to lock ./ibdata1, error: 46
InnoDB: Unable to lock ./ibdata1, error: 46
InnoDB: Unable to lock ./ibdata1, error: 46
InnoDB: Unable to lock ./ibdata1, error: 46
InnoDB: Unable to lock ./ibdata1, error: 46
...
...
050816 11:35:37 InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
050816 11:35:37 InnoDB: Operating system error number 46 in a file operation.
InnoDB: Error number 46 means 'No record locks available'.
InnoDB: Some operating system error numbers are described at
InnoDB:
http://dev.mysql.com/doc/mysql/en/Opera ... codes.html
InnoDB: Could not open or create data files.
InnoDB: If you tried to add new data files, and it failed here,
InnoDB: you should now edit innodb_data_file_path in my.cnf back
InnoDB: to what it was, and remove the new ibdata files InnoDB created
InnoDB: in this failed attempt. InnoDB only wrote those files full of
InnoDB: zeros, but did not yet use them in any way. But be careful: do not
InnoDB: remove old data files which contain your precious data!
050816 11:35:37 [ERROR] Can't init databases
050816 11:35:37 [ERROR] Aborting
050816 11:35:37 [Note] /www/apps/mysql-4.1.13a/libexec/mysqld: Shutdown complete
050816 11:35:43 mysqld ended
<-
My question: am i am right if i say NASLites' intention is only storing files?
Regards, fin.