Description:
Strange errors after restarting the server after a crash.
Seems not handling the UNIX styled directory structure (can not find the databases).
Function seems to be OK.
$ Set NoOn
$ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY"))
050414 14:38:15 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: cannot read directory ./fuji, error 17
InnoDB: cannot read directory ./mpc, error 17
InnoDB: cannot read directory ./mysql, error 17
InnoDB: cannot read directory ./mysql_help, error 17
InnoDB: cannot read directory ./test, error 17
InnoDB: cannot read directory ., error 17
InnoDB: Error: os_file_readdir_next_file returned -1 in MySQL datadir
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
050414 14:38:16 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 224053217.
InnoDB: Doing recovery: scanned up to log sequence number 0 224053217
InnoDB: Last MySQL binlog file position 0 157322924, file name ./SA3-bin.000001
050414 14:38:16 InnoDB: Flushing modified pages from the buffer pool...
050414 14:38:16 InnoDB: Started; log sequence number 0 224053217
050414 14:38:16 [ERROR] Warning: after InnoDB crash recovery, InnoDB says that the binary log of the previous run has the same name
'./SA3-bin.000001' as the current one; this is likely to be abnormal.
/$1$DGA1/sys0/syscommon/mysql/vms/bin/mysqld.exe: ready for connections.
Version: '4.1.9-log' socket: '' port: 3306 Source distribution
How to repeat:
Kill the MYSQL_SERVER process by hand and restart.
Suggested fix:
Not sure, but when the DISK on OpenVMS is formated as ODS-5, it can handle UNIX styled directory path.
Description: Strange errors after restarting the server after a crash. Seems not handling the UNIX styled directory structure (can not find the databases). Function seems to be OK. $ Set NoOn $ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY")) 050414 14:38:15 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: cannot read directory ./fuji, error 17 InnoDB: cannot read directory ./mpc, error 17 InnoDB: cannot read directory ./mysql, error 17 InnoDB: cannot read directory ./mysql_help, error 17 InnoDB: cannot read directory ./test, error 17 InnoDB: cannot read directory ., error 17 InnoDB: Error: os_file_readdir_next_file returned -1 in MySQL datadir InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 050414 14:38:16 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 224053217. InnoDB: Doing recovery: scanned up to log sequence number 0 224053217 InnoDB: Last MySQL binlog file position 0 157322924, file name ./SA3-bin.000001 050414 14:38:16 InnoDB: Flushing modified pages from the buffer pool... 050414 14:38:16 InnoDB: Started; log sequence number 0 224053217 050414 14:38:16 [ERROR] Warning: after InnoDB crash recovery, InnoDB says that the binary log of the previous run has the same name './SA3-bin.000001' as the current one; this is likely to be abnormal. /$1$DGA1/sys0/syscommon/mysql/vms/bin/mysqld.exe: ready for connections. Version: '4.1.9-log' socket: '' port: 3306 Source distribution How to repeat: Kill the MYSQL_SERVER process by hand and restart. Suggested fix: Not sure, but when the DISK on OpenVMS is formated as ODS-5, it can handle UNIX styled directory path.