So, I had forgotten all about these instances, so let's check them now.
The instance with -updates:
It failed with:
+ resize2fs /dev/nvme1n1p1
resize2fs 1.47.0 (5-Feb-2023)
resize2fs: Superblock checksum does not match superblock while trying to open /dev/nvme1n1p1
Couldn't find valid filesystem superblock.
the timestamp is Wed Aug 7 06:42:15 UTC 2024
I started it on... Thu Aug 1 05:46:34 UTC 2024
Okay, this is better than Focal, we lasted 6 days 1 hour.
So we can reproduce the issue.
I then logged into the -proposed instance, with resize2fs 1.47.0-2.4~exp1ubuntu4.1:
It is still running, as of Mon Aug 12 10:49:00 UTC 2024.
This is fantastic. It survived 11 days and 5 hours in the high EBS traffic
us-west-2.
I have terminated the instances now.
The package in -proposed fixes the issue. Happy to mark verified for Noble.
Performing verification for Noble.
So, I had forgotten all about these instances, so let's check them now.
The instance with -updates:
It failed with:
+ resize2fs /dev/nvme1n1p1
resize2fs 1.47.0 (5-Feb-2023)
resize2fs: Superblock checksum does not match superblock while trying to open /dev/nvme1n1p1
Couldn't find valid filesystem superblock.
the timestamp is Wed Aug 7 06:42:15 UTC 2024
I started it on... Thu Aug 1 05:46:34 UTC 2024
Okay, this is better than Focal, we lasted 6 days 1 hour.
So we can reproduce the issue.
I then logged into the -proposed instance, with resize2fs 1.47.0- 2.4~exp1ubuntu4 .1:
It is still running, as of Mon Aug 12 10:49:00 UTC 2024.
This is fantastic. It survived 11 days and 5 hours in the high EBS traffic
us-west-2.
I have terminated the instances now.
The package in -proposed fixes the issue. Happy to mark verified for Noble.