yahoo-eng-team team mailing list archive

[Scott Moser <ssmoser2+ubuntu@xxxxxxxxx>]

The same basic issue is in cloud-init
and had a MP proposed at
 https://code.launchpad.net/~adobrawy/cloud-init/+git/cloud-init/+merge/354680

** Merge proposal linked:
   https://code.launchpad.net/~adobrawy/cloud-init/+git/cloud-init/+merge/354680

** Also affects: cloud-init
   Importance: Undecided
       Status: New

** Changed in: cloud-init
       Status: New => Confirmed

** Changed in: cloud-init
   Importance: Undecided => Medium

-- 
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/1781781

Title:
  /swap.img w/fallocate has holes

Status in cloud-init:
  Confirmed
Status in curtin:
  Confirmed

Bug description:
  The /swap.img file on an XFS root filesystem is not being used. The
  dmesg says it "has holes".

  From the swapon manpage;

  The swap file implementation in the kernel expects to be able to write
  to the file directly, without the assistance of the filesystem.  This
  is a problem on preallocated files (e.g.  fallocate(1)) on filesystems
  like XFS or ext4, and on copy-on-write filesystems like btrfs.

  It is recommended to use dd(1) and /dev/zero to avoid holes on XFS and
  ext4.

  
  I've tracked down this commit which seems to be a step in the right direction;

  https://github.com/CanonicalLtd/curtin/commit/a909966f9c235282267024e86adf404dab83ccfe

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