ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
DistroRelease: Ubuntu 17.10
Ec2AMI: ami-000002da
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
       Users in the 'systemd-journal' group can see all messages. Pass -q to
       turn off this notice.
 No journal files were opened due to insufficient permissions.
Package: linux
PackageArchitecture: amd64
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Tags:  artful ec2-images
Uname: Linux 4.13.0-16-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
_MarkForUpload: True

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1726818

Title:
  vagrant artful64 box filesystem too small

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After building a new vagrant instance using the ubuntu/artful64 box
  (v20171023.1.0), the size of the filesystem seems to be much too
  small. Here's the output of `df -h` on the newly built instance:

  vagrant@ubuntu-artful:~$ df -h
  Filesystem      Size  Used Avail Use% Mounted on
  udev            991M     0  991M   0% /dev
  tmpfs           200M  3.2M  197M   2% /run
  /dev/sda1       2.2G  2.1G   85M  97% /
  tmpfs           999M     0  999M   0% /dev/shm
  tmpfs           5.0M     0  5.0M   0% /run/lock
  tmpfs           999M     0  999M   0% /sys/fs/cgroup
  vagrant         210G  182G   28G  87% /vagrant
  tmpfs           200M     0  200M   0% /run/user/1000

  
  For comparison, here is the same from the latest zesty64 box:

  ubuntu@ubuntu-zesty:~$ df -h
  Filesystem      Size  Used Avail Use% Mounted on
  udev            992M     0  992M   0% /dev
  tmpfs           200M  3.2M  197M   2% /run
  /dev/sda1       9.7G  2.5G  7.3G  26% /
  tmpfs           999M     0  999M   0% /dev/shm
  tmpfs           5.0M     0  5.0M   0% /run/lock
  tmpfs           999M     0  999M   0% /sys/fs/cgroup
  vagrant         210G  183G   28G  88% /vagrant
  tmpfs           200M     0  200M   0% /run/user/1000

  
  With artful64, the size of /dev/sda1 is reported as 2.2G, which results in 
97% of disk usage immediately after building, even though the disk size is 10G, 
as reported by the fdisk:

  
  vagrant@ubuntu-artful:~$ sudo fdisk -l
  Disk /dev/sda: 10 GiB, 10737418240 bytes, 20971520 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x4ad77c39

  Device     Boot Start      End  Sectors Size Id Type
  /dev/sda1  *     2048 20971486 20969439  10G 83 Linux

  
  Disk /dev/sdb: 10 MiB, 10485760 bytes, 20480 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes

  
  Almost any additional installation results in a "No space left on device" 
error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1726818/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to