This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Committed
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1763511
Title:
DataSourceSmartOS should default to ext4
Status in cloud-init:
Fix Released
Status in cloud-init package in Ubuntu:
Fix Released
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/cloud-init/+bug/1763511/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
