Comment 3 for bug 1763511

I think we've been avoiding this issue so far because the file system is
being created without partitioning the disk (layout: False). With "layout:
False", I'm guessing that whether gpt or mbr is specified makes no
difference.

Mike

On Thu, Apr 12, 2018 at 8:41 PM, Scott Moser <email address hidden>
wrote:

> You probably need to change table_type mbr to gpt too if the point is
> big disks. In fact it might just be the mbr table that is limiting you.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1763511
>
> Title:
> DataSourceSmartOS should default to ext4
>
> Status in cloud-init package in Ubuntu:
> New
>
> Bug description:
> As reported in Joyent bug IMAGE-1103, ext3 doesn't work with large
> ephemeral drives.
>
> 2018-03-30 23:36:26,529 - util.py[WARNING]: Failed during filesystem
> operation
> Failed to exec of '['/sbin/mkfs.ext3', '/dev/vdb', '-L', 'ephemeral0',
> '-F']':
> Unexpected error while running command.
> Command: ['/sbin/mkfs.ext3', '/dev/vdb', '-L', 'ephemeral0', '-F']
> Exit code: 1
> Reason: -
> Stdout:
> Stderr: mke2fs 1.42.13 (17-May-2015)
> mkfs.ext3: Size of device (0x100000000 blocks) /dev/vdb too big
> to be expressed
> in 32 bits using a blocksize of 4096.
>
> The default should switch to ext4. It so happens that this matches
> the default in DataSourceAzure.py.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cloud-init/+
> bug/1763511/+subscriptions
>