MySQL 数据库 - 从 webmin 访问时从存储引擎获取错误 28
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/10513887/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
MySQL database - Got error 28 from storage engine while accessing from webmin
提问by govindaraj
I am trying to access an MySQL database from the webmin console. But I'm unable to access the db, as it throws following error message:
我正在尝试从 webmin 控制台访问 MySQL 数据库。但是我无法访问数据库，因为它会引发以下错误消息：
SQL select table_schema,table_name from information_schema.views where table_schema = ?
failed : Got error 28 from storage engine
How can I overcome this problem?
我怎样才能克服这个问题？
回答by Arun G
Check your disk space usage.
检查您的磁盘空间使用情况。
I also faced the same problem. I fixed by moving files into another disk.
我也面临同样的问题。我通过将文件移动到另一个磁盘来修复。
If you are using Linux OS. You can check the disk usage by using the command:
如果您使用的是 Linux 操作系统。您可以使用以下命令检查磁盘使用情况：
> df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/xvda1 8256952 7857928 0 100% /
udev 860884 4 860880 1% /dev
tmpfs 347492 188 347304 1% /run
none 5120 0 5120 0% /run/lock
none 868724 0 868724 0% /run/shm
/dev/xvdb 350891748 199364 332868104 1% /mnt
And I moved some files from /dev/xvda1 -> /dev/xvdb partition.
我从 /dev/xvda1 -> /dev/xvdb 分区移动了一些文件。
And checked the disk usage.
并检查磁盘使用情况。
> df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/xvda1 8256952 2520216 5317308 33% /
udev 860884 4 860880 1% /dev
tmpfs 347492 188 347304 1% /run
none 5120 0 5120 0% /run/lock
none 868724 0 868724 0% /run/shm
/dev/xvdb 350891748 415456 332652012 1% /mnt
Now MySQL server working fine.
现在 MySQL 服务器工作正常。
回答by user2573295
Yes, it is a disk space problem, but it could by masquerade. I suggest open 2 consoles and run in one of them
是的，这是一个磁盘空间问题，但它可以通过伪装。我建议打开 2 个控制台并在其中一个中运行
watch -n1 "df -h"
and on the other try to reproduce the error, at the same time look at the first console. In my case /tmp was at 35% (1G), it goes to 100%, and when the command finish went back to 35%.
另一方面，尝试重现错误，同时查看第一个控制台。在我的情况下，/tmp 为 35% (1G)，它变为 100%，当命令完成时返回到 35%。
回答by Daydah
Actually in my own case, It was a masquerade. I host the site with Siteground, and when I used their SuperCacher to flush the system, everything started working again. I am just adding this answer for anyone in
实际上就我自己而言，这是一场化装舞会。我使用 Siteground 托管该站点，当我使用他们的 SuperCacher 刷新系统时，一切又重新开始工作。我只是为任何人添加这个答案
