{"id":5029,"date":"2025-04-07T09:28:22","date_gmt":"2025-04-07T00:28:22","guid":{"rendered":"https:\/\/mdx.jp\/?post_type=mdx2_news&#038;p=5029"},"modified":"2025-06-03T09:22:33","modified_gmt":"2025-06-03T00:22:33","slug":"%e3%80%90%e9%9a%9c%e5%ae%b3%e6%83%85%e5%a0%b1%e3%80%91mdx%e2%85%b1%e3%82%b7%e3%82%b9%e3%83%86%e3%83%a0%e3%81%ab%e3%81%8a%e3%81%91%e3%82%8b%e3%83%9c%e3%83%aa%e3%83%a5%e3%83%bc%e3%83%a0%e7%a0%b4","status":"publish","type":"mdx2_news","link":"https:\/\/mdx.jp\/en\/mdx2\/news\/5029","title":{"rendered":"(Temporary Fix Completed) Volume Corruption and Snapshot-Related Errors in the mdx\u2161 System"},"content":{"rendered":"<p>(Update as of June 3, 2025)<br \/>\nA temporary fix has been implemented for this error. For more details, please refer to the following:<\/p>\n<blockquote class=\"wp-embedded-content\" data-secret=\"bMCleCeZWH\"><p><a href=\"https:\/\/mdx.jp\/en\/mdx2\/news\/5794\">Announcement of Resumption of mdx  II System Operation and Commencement of GPU Node Services<\/a><\/p><\/blockquote>\n<p><iframe loading=\"lazy\" class=\"wp-embedded-content\" sandbox=\"allow-scripts\" security=\"restricted\" style=\"position: absolute; visibility: hidden;\" title=\"&#8220;Announcement of Resumption of mdx  II System Operation and Commencement of GPU Node Services&#8221; &#8212; mdx\" src=\"https:\/\/mdx.jp\/en\/mdx2\/news\/5794\/embed#?secret=61CaRiZYbL#?secret=bMCleCeZWH\" data-secret=\"bMCleCeZWH\" width=\"500\" height=\"282\" frameborder=\"0\" marginwidth=\"0\" marginheight=\"0\" scrolling=\"no\"><\/iframe><br \/>\n&#8212;-<br \/>\n&nbsp;<br \/>\nCurrently, the following issues are occurring in the mdx\u2161 system.<\/p>\n<h3>1. File system error due to volume corruption of instances<\/h3>\n<h4>\u30fbIssue Description<\/h4>\n<p>In Red Hat OpenStack Platform on mdx\u2161, volume corruption may occur in some instances.<br \/>\nWe have confirmed a problem where the OS of the instance encounters a file system error or becomes read-only either during or after the instance startup.<br \/>\nBelow is an example output of the file system error on the OS when this issue occurs.<\/p>\n<p>\u3010Example output on Ubuntu Server 22.04\u3011  <\/p>\n<table>\n<tr>\n<td>\n#80887: comm rs:main Q:Reg: iget: checksum invalid<br \/>\n[ 9470.149891] EXT4-fs (vda1): Remounting filesystem read-only<br \/>\n[ 9470.151476] EXT4-fs error (device vda1): ext4_lookup:1858: inode\n<\/td>\n<\/tr>\n<\/table>\n<h4>\u30fbCurrent Status:<\/h4>\n<p>The cause of the issue is under investigation.<\/p>\n<p>Based on the current verification results, the issue tends to occur less frequently on Rocky Linux instances.<br \/>\nHowever, we are not in a position to definitively state that the issue does not occur at all on Rocky Linux.<\/p>\n<h4>\u30fbTemporary Measure:<\/h4>\n<p>If a file system error occurs, we apologize for the inconvenience, but please contact us via the <a href=\"https:\/\/mdx.jp\/mdx2\/p\/contact\">inquiry form<\/a>.<br \/>\nRecovery will be performed using one of the following methods:<\/p>\n<table>\n<tr>\n<td>\n\u30fbRepairing the file system using fsck<br \/>\n\u30fbRestoring from a backup of the volume file<br \/>\n \u203b The system performs a daily backup of volume files at 1:00 AM.<br \/>\n   If recovery is performed from a backup, the data may revert to a state from as early as 1 day to as late as 2 weeks ago.\n<\/td>\n<\/tr>\n<\/table>\n<h3>2. Error when creating a volume from instance or volume snapshot<\/h3>\n<p><code>Due to the maintenance scheduled from May 19 to May 21, 2025, the issue with the snapshot feature is expected to be resolved, and it should be functioning normally after the maintenance is completed.<\/code><\/p>\n<h4>\u30fbIssue Description:<\/h4>\n<p>In Red Hat OpenStack Platform on mdx\u2161, we have confirmed a problem where creating a new volume from a snapshot taken from an instance or volume results in an error if it&#8217;s the second or later snapshot.<br \/>\nThis issue occurs under the following procedures when creating a volume from a second or later snapshot of an instance or volume:<\/p>\n<p><strong>\u3010Creating a volume from an instance snapshot\u3011<\/strong><\/p>\n<table>\n<tr>\n<td>\n    (1) Log in to the user portal<br \/>\n    (2) Click [Project] menu > [Compute] panel > [Instances] tab<br \/>\n    (3) In the Actions column of the instance you want to snapshot, click [Create Snapshot]<br \/>\n        \u2192 This issue occurs when using snapshots taken from the second time onward<br \/>\n    (4) Click [Project] menu > [Compute] panel > [Images] tab<br \/>\n    (5) From the dropdown menu at the right end of the snapshot, click [Create Volume] to create a volume\n<\/td>\n<\/tr>\n<\/table>\n<p>&nbsp;<br \/>\n<strong>\u3010Creating a volume from a volume snapshot\u3011<\/strong><\/p>\n<table>\n<tr>\n<td>\n    (1) Log in to the user portal<br \/>\n    (2) Click [Project] menu > [Volumes] panel > [Volumes] tab<br \/>\n    (3) In the Actions column of the volume you want to snapshot, click [Create Snapshot]<br \/>\n        \u2192 This issue occurs when using snapshots taken from the second time onward<br \/>\n    (4) Click [Project] menu > [Volumes] panel > [Snapshots] tab<br \/>\n    (5) From the dropdown menu at the right end of the snapshot, click [Create Volume] to create a volume\n<\/td>\n<\/tr>\n<\/table>\n<h4>\u30fbCurrent Status:<\/h4>\n<p>This is a known issue with Red Hat OpenStack Platform and is currently under investigation.<\/p>\n<h4>\u30fbTemporary Measure:<\/h4>\n<p>To mitigate this issue, we have temporarily hidden the following actions and tabs on the user portal.<br \/>\nWe apologize for the inconvenience, but until the issue is resolved, snapshot operations for instances and volumes will not be available.<\/p>\n<table>\n<tr>\n<td>\n    + The [Create Snapshot] action in step (3) of \u3010Creating a volume from an instance snapshot\u3011 is hidden<br \/>\n    + The [Snapshots] tab in step (4) of \u3010Creating a volume from a volume snapshot\u3011 is hidden\n<\/td>\n<\/tr>\n<\/table>\n<p>&nbsp;<br \/>\nWe apologize for the inconvenience and appreciate your understanding.<\/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,"jetpack_seo_schema_type":""},"mdx2_news-cat":[124858],"class_list":["post-5029","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\/5029","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":4,"href":"https:\/\/mdx.jp\/wp-json\/wp\/v2\/mdx2_news\/5029\/revisions"}],"predecessor-version":[{"id":5825,"href":"https:\/\/mdx.jp\/wp-json\/wp\/v2\/mdx2_news\/5029\/revisions\/5825"}],"wp:attachment":[{"href":"https:\/\/mdx.jp\/wp-json\/wp\/v2\/media?parent=5029"}],"wp:term":[{"taxonomy":"mdx2_news-cat","embeddable":true,"href":"https:\/\/mdx.jp\/wp-json\/wp\/v2\/mdx2_news-cat?post=5029"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}