Mixing
Cannot resize Google Cloud persistent disk
0
I'm trying to resize an Ext4 Google Cloud persistent disk from 14TB to 15 TB. I have an instance running Centos6. I increased the size of the disk in the cloud console. Now when I unmount the disk and try to run resize2fs it fails with this this error:
sudo resize2fs /dev/sdb
resize2fs 1.41.12 (17-May-2010)
resize2fs: Filesystem has unsupported feature(s) while trying to open
/dev/sdb
Couldn't find valid filesystem superblock.
Any ideas or advice would be appreciated.
Thanks.
google-cloud-platform google-compute-engine ext4 google-persistent-disk
edited Dec 14 '18 at 20:02
José CM
395
asked Nov 22 '18 at 8:56
as252522as252522
11
|
show 8 more comments
0
I'm trying to resize an Ext4 Google Cloud persistent disk from 14TB to 15 TB. I have an instance running Centos6. I increased the size of the disk in the cloud console. Now when I unmount the disk and try to run resize2fs it fails with this this error:
sudo resize2fs /dev/sdb
resize2fs 1.41.12 (17-May-2010)
resize2fs: Filesystem has unsupported feature(s) while trying to open
/dev/sdb
Couldn't find valid filesystem superblock.
Any ideas or advice would be appreciated.
Thanks.
google-cloud-platform google-compute-engine ext4 google-persistent-disk
edited Dec 14 '18 at 20:02
José CM
395
asked Nov 22 '18 at 8:56
as252522as252522
11
Most likely the file system that you want to resize is not the disk device/dev/sdbbut instead a partition on the device like/dev/sdb1. The commandfdisk -lwill list your disk partitions. Another possibility is that the file system is not EXT2. You would then need to use a file sytem resize command for that type of file system.
– John Hanley
Nov 22 '18 at 18:12
Disk /dev/sdb: 16106.1 GB, 16106127360000 bytes 255 heads, 63 sectors/track, 1958125 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000
– as252522
Nov 22 '18 at 19:22
It doesn't look like it is partitioned from the result of fdisk. It is definitely EXT4.
– as252522
Nov 22 '18 at 19:24
I overlooked the TB part of your question. MBR partitioned disks cannot be larger than 2 TB, so this must be raw formatted (e.g. no partition table). How are you sure that this is EXT4? How did you put a file sytem on this disk previously? You are very close to the max size for EXT4, so I would make sure that I have a backup in case you break the file system.
– John Hanley
Nov 22 '18 at 19:35
I've been using the partition for the past 4 months. I formatted it with: sudo mkfs.ext4 -m 0 -F -E lazy_itable_init=0,lazy_journal_init=0,discard /dev/sdb
– as252522
Nov 22 '18 at 20:26
|
show 8 more comments
0
0
0
I'm trying to resize an Ext4 Google Cloud persistent disk from 14TB to 15 TB. I have an instance running Centos6. I increased the size of the disk in the cloud console. Now when I unmount the disk and try to run resize2fs it fails with this this error:
sudo resize2fs /dev/sdb
resize2fs 1.41.12 (17-May-2010)
resize2fs: Filesystem has unsupported feature(s) while trying to open
/dev/sdb
Couldn't find valid filesystem superblock.
Any ideas or advice would be appreciated.
Thanks.
google-cloud-platform google-compute-engine ext4 google-persistent-disk
edited Dec 14 '18 at 20:02
José CM
395
asked Nov 22 '18 at 8:56
as252522as252522
11
I'm trying to resize an Ext4 Google Cloud persistent disk from 14TB to 15 TB. I have an instance running Centos6. I increased the size of the disk in the cloud console. Now when I unmount the disk and try to run resize2fs it fails with this this error:
sudo resize2fs /dev/sdb
resize2fs 1.41.12 (17-May-2010)
resize2fs: Filesystem has unsupported feature(s) while trying to open
/dev/sdb
Couldn't find valid filesystem superblock.
Any ideas or advice would be appreciated.
Thanks.
google-cloud-platform google-compute-engine ext4 google-persistent-disk
google-cloud-platform google-compute-engine ext4 google-persistent-disk
edited Dec 14 '18 at 20:02
José CM
395
asked Nov 22 '18 at 8:56
as252522as252522
11
edited Dec 14 '18 at 20:02
José CM
395
asked Nov 22 '18 at 8:56
as252522as252522
11
edited Dec 14 '18 at 20:02
José CM
395
edited Dec 14 '18 at 20:02
José CM
395
edited Dec 14 '18 at 20:02
José CM
395
395
asked Nov 22 '18 at 8:56
as252522as252522
11
asked Nov 22 '18 at 8:56
as252522as252522
11
asked Nov 22 '18 at 8:56
as252522as252522
11
11
Most likely the file system that you want to resize is not the disk device/dev/sdbbut instead a partition on the device like/dev/sdb1. The commandfdisk -lwill list your disk partitions. Another possibility is that the file system is not EXT2. You would then need to use a file sytem resize command for that type of file system.
– John Hanley
Nov 22 '18 at 18:12
Disk /dev/sdb: 16106.1 GB, 16106127360000 bytes 255 heads, 63 sectors/track, 1958125 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000
– as252522
Nov 22 '18 at 19:22
It doesn't look like it is partitioned from the result of fdisk. It is definitely EXT4.
– as252522
Nov 22 '18 at 19:24
I overlooked the TB part of your question. MBR partitioned disks cannot be larger than 2 TB, so this must be raw formatted (e.g. no partition table). How are you sure that this is EXT4? How did you put a file sytem on this disk previously? You are very close to the max size for EXT4, so I would make sure that I have a backup in case you break the file system.
– John Hanley
Nov 22 '18 at 19:35
I've been using the partition for the past 4 months. I formatted it with: sudo mkfs.ext4 -m 0 -F -E lazy_itable_init=0,lazy_journal_init=0,discard /dev/sdb
– as252522
Nov 22 '18 at 20:26
|
show 8 more comments
Most likely the file system that you want to resize is not the disk device/dev/sdbbut instead a partition on the device like/dev/sdb1. The commandfdisk -lwill list your disk partitions. Another possibility is that the file system is not EXT2. You would then need to use a file sytem resize command for that type of file system.
– John Hanley
Nov 22 '18 at 18:12
Disk /dev/sdb: 16106.1 GB, 16106127360000 bytes 255 heads, 63 sectors/track, 1958125 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000
– as252522
Nov 22 '18 at 19:22
It doesn't look like it is partitioned from the result of fdisk. It is definitely EXT4.
– as252522
Nov 22 '18 at 19:24
I overlooked the TB part of your question. MBR partitioned disks cannot be larger than 2 TB, so this must be raw formatted (e.g. no partition table). How are you sure that this is EXT4? How did you put a file sytem on this disk previously? You are very close to the max size for EXT4, so I would make sure that I have a backup in case you break the file system.
– John Hanley
Nov 22 '18 at 19:35
I've been using the partition for the past 4 months. I formatted it with: sudo mkfs.ext4 -m 0 -F -E lazy_itable_init=0,lazy_journal_init=0,discard /dev/sdb
– as252522
Nov 22 '18 at 20:26
Most likely the file system that you want to resize is not the disk device
/dev/sdb but instead a partition on the device like /dev/sdb1. The command fdisk -l will list your disk partitions. Another possibility is that the file system is not EXT2. You would then need to use a file sytem resize command for that type of file system.– John Hanley
Nov 22 '18 at 18:12
Most likely the file system that you want to resize is not the disk device
/dev/sdb but instead a partition on the device like /dev/sdb1. The command fdisk -l will list your disk partitions. Another possibility is that the file system is not EXT2. You would then need to use a file sytem resize command for that type of file system.– John Hanley
Nov 22 '18 at 18:12
Disk /dev/sdb: 16106.1 GB, 16106127360000 bytes 255 heads, 63 sectors/track, 1958125 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000
– as252522
Nov 22 '18 at 19:22
Disk /dev/sdb: 16106.1 GB, 16106127360000 bytes 255 heads, 63 sectors/track, 1958125 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000
– as252522
Nov 22 '18 at 19:22
It doesn't look like it is partitioned from the result of fdisk. It is definitely EXT4.
– as252522
Nov 22 '18 at 19:24
It doesn't look like it is partitioned from the result of fdisk. It is definitely EXT4.
– as252522
Nov 22 '18 at 19:24
I overlooked the TB part of your question. MBR partitioned disks cannot be larger than 2 TB, so this must be raw formatted (e.g. no partition table). How are you sure that this is EXT4? How did you put a file sytem on this disk previously? You are very close to the max size for EXT4, so I would make sure that I have a backup in case you break the file system.
– John Hanley
Nov 22 '18 at 19:35
I overlooked the TB part of your question. MBR partitioned disks cannot be larger than 2 TB, so this must be raw formatted (e.g. no partition table). How are you sure that this is EXT4? How did you put a file sytem on this disk previously? You are very close to the max size for EXT4, so I would make sure that I have a backup in case you break the file system.
– John Hanley
Nov 22 '18 at 19:35
I've been using the partition for the past 4 months. I formatted it with: sudo mkfs.ext4 -m 0 -F -E lazy_itable_init=0,lazy_journal_init=0,discard /dev/sdb
– as252522
Nov 22 '18 at 20:26
I've been using the partition for the past 4 months. I formatted it with: sudo mkfs.ext4 -m 0 -F -E lazy_itable_init=0,lazy_journal_init=0,discard /dev/sdb
– as252522
Nov 22 '18 at 20:26
|
show 8 more comments
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53427111%2fcannot-resize-google-cloud-persistent-disk%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53427111%2fcannot-resize-google-cloud-persistent-disk%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Most likely the file system that you want to resize is not the disk device
/dev/sdbbut instead a partition on the device like/dev/sdb1. The commandfdisk -lwill list your disk partitions. Another possibility is that the file system is not EXT2. You would then need to use a file sytem resize command for that type of file system.– John Hanley
Nov 22 '18 at 18:12
Disk /dev/sdb: 16106.1 GB, 16106127360000 bytes 255 heads, 63 sectors/track, 1958125 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000
– as252522
Nov 22 '18 at 19:22
It doesn't look like it is partitioned from the result of fdisk. It is definitely EXT4.
– as252522
Nov 22 '18 at 19:24
I overlooked the TB part of your question. MBR partitioned disks cannot be larger than 2 TB, so this must be raw formatted (e.g. no partition table). How are you sure that this is EXT4? How did you put a file sytem on this disk previously? You are very close to the max size for EXT4, so I would make sure that I have a backup in case you break the file system.
– John Hanley
Nov 22 '18 at 19:35
I've been using the partition for the past 4 months. I formatted it with: sudo mkfs.ext4 -m 0 -F -E lazy_itable_init=0,lazy_journal_init=0,discard /dev/sdb
– as252522
Nov 22 '18 at 20:26