网站建设seo优化,网站建设发展历程ppt,古蔺网站建设,昆明小程序开发公司哪家好mysql bug#xff08; InnoDB: Error number 22#xff09;#xff0c;表突然不能读取 bug最开始的bug#xff1a;表突然不能读取关闭mysql容器#xff0c;再次重启失败 解决方案不重建容器的几种可能措施重建容器重建如果懒得打命令或者忘记命令可能的run bug#xff1a… mysql bug InnoDB: Error number 22表突然不能读取 bug最开始的bug表突然不能读取关闭mysql容器再次重启失败 解决方案不重建容器的几种可能措施重建容器重建如果懒得打命令或者忘记命令可能的run bugxxxx file exists. bug
最开始的bug表突然不能读取
2024-03-06 15:06:11 2024-03-06T07:06:11.137389Z 17 [ERROR] InnoDB: Error number 22 means Invalid argument
2024-03-06 15:06:11 2024-03-06T07:06:11.137394Z 17 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2024-03-06 15:06:11 2024-03-06T07:06:11.137397Z 17 [ERROR] InnoDB: File ./webbuild/sys_config.frm: stat returned OS error 122.关闭mysql容器再次重启失败
2024-03-06 15:07:25 2024-03-06T07:07:25.883653Z 0 [ERROR] InnoDB: Operating system error number 22 in a file operation.
2024-03-06 15:07:25 2024-03-06T07:07:25.883688Z 0 [ERROR] InnoDB: Error number 22 means Invalid argument
2024-03-06 15:07:25 2024-03-06T07:07:25.883695Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2024-03-06 15:07:25 2024-03-06T07:07:25.883698Z 0 [ERROR] InnoDB: File .//ib_buffer_pool: stat returned OS error 122.
2024-03-06 15:07:25 2024-03-06T07:07:25.883703Z 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
2024-03-06 15:07:25 2024-03-06T07:07:25.883877Z 0 [ERROR] InnoDB: Cannot open /var/lib/mysql/ib_buffer_pool.incomplete for writing: Invalid argument
2024-03-06 15:07:26 2024-03-06T07:07:26.585788Z 0 [ERROR] InnoDB: Operating system error number 5 in a file operation.
2024-03-06 15:07:26 2024-03-06T07:07:26.585931Z 0 [ERROR] InnoDB: Error number 5 means Input/output error
2024-03-06 15:07:26 2024-03-06T07:07:26.585953Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2024-03-06 15:07:26 2024-03-06T07:07:26.585967Z 0 [ERROR] InnoDB: File ./ib_logfile0: Linux aio returned OS error 105. Cannot continue operation
2024-03-06 15:07:26 2024-03-06T07:07:26.585975Z 0 [ERROR] InnoDB: Cannot continue operation.
2024-03-05 13:42:51 2024-03-05 05:42:5100:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.44-1.el7 started.
2024-03-05 13:42:51 2024-03-05 05:42:5100:00 [Note] [Entrypoint]: Switching to dedicated user mysql
2024-03-05 13:42:51 2024-03-05 05:42:5100:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.44-1.el7 started.
2024-03-05 13:42:52 /var/lib/mysql/mysql.sock - /var/run/mysqld/mysqld.sock解决方案
不重建容器的几种可能措施
关键的信息
File ./webbuild/sys_config.frm: ‘stat’ returned OS error 122.Operating system error number 22 in a file operation.File .//ib_buffer_pool: ‘stat’ returned OS error 122.Cannot open /var/lib/mysql/ib_buffer_pool.incomplete’ for writing: Invalid argumentFile ./ib_logfile0: ‘Linux aio’ returned OS error 105. Cannot continue operation‘/var/lib/mysql/mysql.sock’ - ‘/var/run/mysqld/mysqld.sock’
查了下有以下几种可能
dokcer在windows上的文件系统兼容问题‘Linux aio’重启docker(优先建议这种方法docker引擎在window很容易出问题)我的sys_config表的stat字段有问题移除它的表文件容器内存不够mysql的缓存页空间不足ib_buffer_pooldocker update扩容logfile文件问题备份并移除logfile文件./ib_logfile0
除了重启没试过其他试了都没有我就重建容器了因为其他容器正常就没第一时间怀疑docker后面还是重启docker解决
重建容器
重建
docker run --envMYSQL_ROOT_PASSWORDxxxx --envPATH/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin --envGOSU_VERSION1.16 --envMYSQL_MAJOR5.7 --envMYSQL_VERSION5.7.44-1.el7 --envMYSQL_SHELL_VERSION8.0.35-1.el7 --volumeE:\volume\mysql\mysql5.7\conf:/etc/mysql/conf.d --volumeE:\volume\mysql\mysql5.7\data:/var/lib/mysql --volumeE:\volume\mysql\mysql5.7\log:/var/log --volume/var/lib/mysql -p 3306:3306 --restartno --runtimerunc --memory1073741824 -d mysql:5.7如果懒得打命令或者忘记命令
2种方式
docker desktop软件docker commit 可能的run bugxxxx file exists.
docker: Error response from daemon: error while creating mount source path /run/desktop/mnt/host/e/volume/mysql/mysql5.7/data: mkdir /run/desktop/mnt/host/e: file exists.docker在windows上的兼容问题将docker重启一下再次run ok 说明最开始的mysql bug应该就是docker的文件系统兼容问题应该重启docker就行不用重建
