https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudera-Manager-root-volume-does-not-get-resized/m-p/21715#M3764 <P>Fixed by picking a different AMI, the original AMI had multiple partitions on the root disk which the director install did not appreciate. Switching to an AMI with a single partition on the root volume appears to have resolved this issue entirely. FWIW the picking the official centos AMI should ensure you dont have a bad time.</P> Mon, 17 Nov 2014 22:34:39 GMT jwm 2014-11-17T22:34:39Z https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudera-Manager-root-volume-does-not-get-resized/m-p/21712#M3763 <P>After launching a new manager node I discovered the root volume was not resized to the provisioned limit.</P><P>&nbsp;</P><P># lsblk<BR />NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT<BR />xvda 202:0 0 250G 0 disk<BR />├─xvda1 202:1 0 200M 0 part /boot<BR />├─xvda2 202:2 0 4G 0 part [SWAP]<BR />└─xvda3 202:3 0 10.8G 0 part /</P> Fri, 16 Sep 2022 09:13:25 GMT https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudera-Manager-root-volume-does-not-get-resized/m-p/21712#M3763 jwm 2022-09-16T09:13:25Z https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudera-Manager-root-volume-does-not-get-resized/m-p/21715#M3764 <P>Fixed by picking a different AMI, the original AMI had multiple partitions on the root disk which the director install did not appreciate. Switching to an AMI with a single partition on the root volume appears to have resolved this issue entirely. FWIW the picking the official centos AMI should ensure you dont have a bad time.</P> Mon, 17 Nov 2014 22:34:39 GMT https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudera-Manager-root-volume-does-not-get-resized/m-p/21715#M3764 jwm 2014-11-17T22:34:39Z