kernel-packages team mailing list archive

[Joseph Salisbury <joseph.salisbury@xxxxxxxxxxxxx>]

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Tags added: kernel-da-key trusty utopic

** No longer affects: linux

** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu Utopic)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu Trusty)
       Status: New => Confirmed

** Changed in: linux (Ubuntu Utopic)
       Status: New => Confirmed

** Changed in: linux (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Utopic)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1434914

Title:
  xfs_growfs fails to allocate new inodes in Ubuntu Trusty

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Utopic:
  Confirmed

Bug description:
  Release:
  Description:    Ubuntu 14.04.2 LTS
  Release:        14.04

  Packages:
  linux-image-3.13.0-46-generic    3.13.0-46.79
  xfsprogs                         3.1.9ubuntu2

  When using xfs_growfs to grow an xfs filesystem, inodes on the grown
  portion of the filesystem are not available for writing, leading to
  ENOSPC errors even when free disk space and unused inodes are reported
  by df -i and df.

  Actual results:
  A worker creating many files, will run out of inode space as if the fs was not grown.

  Expected results:
  A worker creating many files, will continue to create new files for the grown fs.

  mount -o remount,inode64 /mnt/point fixes this issue and allows
  further writes to the grown fs.

  More information and reproduction steps can be found in this bug
  report: https://bugzilla.redhat.com/show_bug.cgi?id=1115201

  Also, the LXC FAQ has a description that indicates this bug has been
  present since kernel 3.7. It also offers the work around I wrote
  above:
  http://xfs.org/index.php/XFS_FAQ#Q:_Why_do_I_receive_No_space_left_on_device_after_xfs_growfs.3F

  This bug has been fixed upstream in 3.17:
  https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=9de67c3ba9ea961ba420573d56479d09d33a7587

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1434914/+subscriptions