(Update at 19:50, August 12)<\/p>\n
The file system consistency checks (fsck) on the volumes of the affected instances were completed at approximately 19:30 on August 12. We sincerely apologize for the prolonged inconvenience and concern this may have caused. (Update at 18:00, August 12)<\/p>\n Investigation and initial response to this incident have been completed.<\/p>\n [Summary of the Incident] Unable to read or write files<\/p>\n Unable to access instances via SSH [Current Status] [Next Steps] We apologize for the extended disruption and appreciate your patience and understanding as we continue to address the matter.<\/p>\n —-<\/p>\n As of August 12, 4:30 PM, we have confirmed that file system I\/O errors are occurring on some instances in the mdxII OpenStack environment. If you encounter any irregularities or errors in file read\/write operations on your instances, please contact our emergency support desk immediately:<\/p>\n mdxII Emergency Support Desk Please note that we may conduct emergency maintenance if deemed necessary.<\/p>\n We sincerely apologize for the inconvenience this may cause and appreciate your understanding and cooperation.<\/p>\n","protected":false},"featured_media":0,"parent":0,"template":"","meta":{"_acf_changed":false,"advanced_seo_description":"","jetpack_seo_html_title":"","jetpack_seo_noindex":false},"mdx2_news-cat":[124858],"class_list":["post-7113","mdx2_news","type-mdx2_news","status-publish","hentry","mdx2_news-cat-accident","en-US"],"acf":[],"jetpack_likes_enabled":true,"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/mdx.jp\/wp-json\/wp\/v2\/mdx2_news\/7113","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mdx.jp\/wp-json\/wp\/v2\/mdx2_news"}],"about":[{"href":"https:\/\/mdx.jp\/wp-json\/wp\/v2\/types\/mdx2_news"}],"version-history":[{"count":8,"href":"https:\/\/mdx.jp\/wp-json\/wp\/v2\/mdx2_news\/7113\/revisions"}],"predecessor-version":[{"id":7127,"href":"https:\/\/mdx.jp\/wp-json\/wp\/v2\/mdx2_news\/7113\/revisions\/7127"}],"wp:attachment":[{"href":"https:\/\/mdx.jp\/wp-json\/wp\/v2\/media?parent=7113"}],"wp:term":[{"taxonomy":"mdx2_news-cat","embeddable":true,"href":"https:\/\/mdx.jp\/wp-json\/wp\/v2\/mdx2_news-cat?post=7113"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nAll recovery work related to this incident has now been completed, and the mdxII system is fully operational.<\/strong><\/p>\n
\n—-<\/p>\n
\nOn August 12, following hardware replacement work, it was confirmed that this issue began occurring at approximately 14:24.
\nAs a result, for instances that were running at 14:24, the following conditions occurred:<\/p>\n
\nAdditionally, it was not possible to launch new instances during this period.
\nWe sincerely apologize for the inconvenience caused.<\/p>\n
\nAs of 17:10, August 12, the restart of affected instances has been completed, and the issue has been resolved.
\nLaunching new instances is also now possible.<\/p>\n
\nWe are currently performing file system integrity checks (fsck) on the volumes of the affected instances.
\nThis work is expected to be completed around 19:30 today, and we will provide an update once it is finished.<\/p>\n
\nSimilar issues have been reported in multiple projects, and we are currently investigating the cause.<\/p>\n
\nmdx2-support@hpc.cmc.osaka-u.ac.jp<\/p>\n