What is the Max file system size limit -Ubuntu KVM
There were VMs which was created using 5TB disk size in the flavor but getting only 2TB for file system when VM is spawning.
Is there any limit for maximum file system size for VM which are running in KVM or any other issue with these environment.
Current 2TB limitation belong to MBR partition tables, those are not able to address more than 2TB of data.
As we can’t use MBR tables for 5TB disk , we have been checking the option of define GPT partition
tables by cloud-init definition, for that We tried using the following user data file
disk_setup:
/dev/vda:
table_type: 'gpt'
layout:
- 10
- 90
overwrite: true
fs_setup:
- label: root_fs
filesystem: 'ext4'
device: /dev/vda
partition: vda1
overwrite: true
- label: data_disk
filesystem: 'ext4'
device: /dev/vda
partition: vda2
overwrite: true
But, this commands wasn’t executed in Instance creation, We realized that “disk_setup” module is
not loaded in cloud init, that is, inside VM file ” /etc/cloud/cloud.cfg” not appear the module
loaded, appeared in the following:
cloud_config_modules:
- mounts
- locale
- set-passwords
- rh_subscription
- yum-add-repo
- package-update-upgrade-install
- timezone
- puppet
- chef
- salt-minion
- mcollective
- disable-ec2-metadata
- runcmd
And should be
cloud_config_modules:
- disk_setup
- mounts
- locale
- set-passwords
- rh_subscription
- yum-add-repo
- package-update-upgrade-install
- timezone
- puppet
- chef
- salt-minion
- mcollective
- disable-ec2-metadata
- runcmd
After change that, we removed all files from /var/lib/cloud/ and rebooted the instance to force
cloud-init execution, in that moment GPT partition table modification is executed but filesystem
configuration was not, We made the filesystem configuration manually and we were able of have 5TB
disk in use. But the bad part is, due to this Instance is using BIOS (SeaBIOS) and not UEFI, after
modify partition table to GPT, VM instance isn’t able to boot again.
For this reason, we need your support by checking correct configuration of cloud-init to execute
all commands defined in user data file in VM instance creation.
NAME=Mitaka on Ubuntu 14.04
14.04
edited Feb 21 at 15:37
Mr Shunz
2,49121922
asked Feb 21 at 14:38
NithiyaNithiya
62
add a comment |
There were VMs which was created using 5TB disk size in the flavor but getting only 2TB for file system when VM is spawning.
Is there any limit for maximum file system size for VM which are running in KVM or any other issue with these environment.
Current 2TB limitation belong to MBR partition tables, those are not able to address more than 2TB of data.
As we can’t use MBR tables for 5TB disk , we have been checking the option of define GPT partition
tables by cloud-init definition, for that We tried using the following user data file
disk_setup:
/dev/vda:
table_type: 'gpt'
layout:
- 10
- 90
overwrite: true
fs_setup:
- label: root_fs
filesystem: 'ext4'
device: /dev/vda
partition: vda1
overwrite: true
- label: data_disk
filesystem: 'ext4'
device: /dev/vda
partition: vda2
overwrite: true
But, this commands wasn’t executed in Instance creation, We realized that “disk_setup” module is
not loaded in cloud init, that is, inside VM file ” /etc/cloud/cloud.cfg” not appear the module
loaded, appeared in the following:
cloud_config_modules:
- mounts
- locale
- set-passwords
- rh_subscription
- yum-add-repo
- package-update-upgrade-install
- timezone
- puppet
- chef
- salt-minion
- mcollective
- disable-ec2-metadata
- runcmd
And should be
cloud_config_modules:
- disk_setup
- mounts
- locale
- set-passwords
- rh_subscription
- yum-add-repo
- package-update-upgrade-install
- timezone
- puppet
- chef
- salt-minion
- mcollective
- disable-ec2-metadata
- runcmd
After change that, we removed all files from /var/lib/cloud/ and rebooted the instance to force
cloud-init execution, in that moment GPT partition table modification is executed but filesystem
configuration was not, We made the filesystem configuration manually and we were able of have 5TB
disk in use. But the bad part is, due to this Instance is using BIOS (SeaBIOS) and not UEFI, after
modify partition table to GPT, VM instance isn’t able to boot again.
For this reason, we need your support by checking correct configuration of cloud-init to execute
all commands defined in user data file in VM instance creation.
NAME=Mitaka on Ubuntu 14.04
14.04
edited Feb 21 at 15:37
Mr Shunz
2,49121922
asked Feb 21 at 14:38
NithiyaNithiya
62
add a comment |
There were VMs which was created using 5TB disk size in the flavor but getting only 2TB for file system when VM is spawning.
Is there any limit for maximum file system size for VM which are running in KVM or any other issue with these environment.
Current 2TB limitation belong to MBR partition tables, those are not able to address more than 2TB of data.
As we can’t use MBR tables for 5TB disk , we have been checking the option of define GPT partition
tables by cloud-init definition, for that We tried using the following user data file
disk_setup:
/dev/vda:
table_type: 'gpt'
layout:
- 10
- 90
overwrite: true
fs_setup:
- label: root_fs
filesystem: 'ext4'
device: /dev/vda
partition: vda1
overwrite: true
- label: data_disk
filesystem: 'ext4'
device: /dev/vda
partition: vda2
overwrite: true
But, this commands wasn’t executed in Instance creation, We realized that “disk_setup” module is
not loaded in cloud init, that is, inside VM file ” /etc/cloud/cloud.cfg” not appear the module
loaded, appeared in the following:
cloud_config_modules:
- mounts
- locale
- set-passwords
- rh_subscription
- yum-add-repo
- package-update-upgrade-install
- timezone
- puppet
- chef
- salt-minion
- mcollective
- disable-ec2-metadata
- runcmd
And should be
cloud_config_modules:
- disk_setup
- mounts
- locale
- set-passwords
- rh_subscription
- yum-add-repo
- package-update-upgrade-install
- timezone
- puppet
- chef
- salt-minion
- mcollective
- disable-ec2-metadata
- runcmd
After change that, we removed all files from /var/lib/cloud/ and rebooted the instance to force
cloud-init execution, in that moment GPT partition table modification is executed but filesystem
configuration was not, We made the filesystem configuration manually and we were able of have 5TB
disk in use. But the bad part is, due to this Instance is using BIOS (SeaBIOS) and not UEFI, after
modify partition table to GPT, VM instance isn’t able to boot again.
For this reason, we need your support by checking correct configuration of cloud-init to execute
all commands defined in user data file in VM instance creation.
NAME=Mitaka on Ubuntu 14.04
14.04
edited Feb 21 at 15:37
Mr Shunz
2,49121922
asked Feb 21 at 14:38
NithiyaNithiya
62
There were VMs which was created using 5TB disk size in the flavor but getting only 2TB for file system when VM is spawning.
Is there any limit for maximum file system size for VM which are running in KVM or any other issue with these environment.
Current 2TB limitation belong to MBR partition tables, those are not able to address more than 2TB of data.
As we can’t use MBR tables for 5TB disk , we have been checking the option of define GPT partition
tables by cloud-init definition, for that We tried using the following user data file
disk_setup:
/dev/vda:
table_type: 'gpt'
layout:
- 10
- 90
overwrite: true
fs_setup:
- label: root_fs
filesystem: 'ext4'
device: /dev/vda
partition: vda1
overwrite: true
- label: data_disk
filesystem: 'ext4'
device: /dev/vda
partition: vda2
overwrite: true
But, this commands wasn’t executed in Instance creation, We realized that “disk_setup” module is
not loaded in cloud init, that is, inside VM file ” /etc/cloud/cloud.cfg” not appear the module
loaded, appeared in the following:
cloud_config_modules:
- mounts
- locale
- set-passwords
- rh_subscription
- yum-add-repo
- package-update-upgrade-install
- timezone
- puppet
- chef
- salt-minion
- mcollective
- disable-ec2-metadata
- runcmd
And should be
cloud_config_modules:
- disk_setup
- mounts
- locale
- set-passwords
- rh_subscription
- yum-add-repo
- package-update-upgrade-install
- timezone
- puppet
- chef
- salt-minion
- mcollective
- disable-ec2-metadata
- runcmd
After change that, we removed all files from /var/lib/cloud/ and rebooted the instance to force
cloud-init execution, in that moment GPT partition table modification is executed but filesystem
configuration was not, We made the filesystem configuration manually and we were able of have 5TB
disk in use. But the bad part is, due to this Instance is using BIOS (SeaBIOS) and not UEFI, after
modify partition table to GPT, VM instance isn’t able to boot again.
For this reason, we need your support by checking correct configuration of cloud-init to execute
all commands defined in user data file in VM instance creation.
NAME=Mitaka on Ubuntu 14.04
14.04
14.04
edited Feb 21 at 15:37
Mr Shunz
2,49121922
asked Feb 21 at 14:38
NithiyaNithiya
62
edited Feb 21 at 15:37
Mr Shunz
2,49121922
asked Feb 21 at 14:38
NithiyaNithiya
62
edited Feb 21 at 15:37
Mr Shunz
2,49121922
edited Feb 21 at 15:37
Mr Shunz
2,49121922
edited Feb 21 at 15:37
Mr Shunz
2,49121922
2,49121922
asked Feb 21 at 14:38
NithiyaNithiya
62
asked Feb 21 at 14:38
NithiyaNithiya
62
asked Feb 21 at 14:38
NithiyaNithiya
62
62
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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
});
}
});
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%2faskubuntu.com%2fquestions%2f1120144%2fwhat-is-the-max-file-system-size-limit-ubuntu-kvm%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
Thanks for contributing an answer to Ask Ubuntu!
- 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.
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%2faskubuntu.com%2fquestions%2f1120144%2fwhat-is-the-max-file-system-size-limit-ubuntu-kvm%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
