`df /dev/sda1` no longer reports information for /dev/sda1
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
coreutils (Ubuntu) | ||||||
Trusty |
Fix Released
|
Medium
|
Dave Chiluk | |||
initramfs-tools (Ubuntu) | ||||||
Trusty |
Fix Released
|
Medium
|
Dave Chiluk |
Bug Description
[Impact]
* df fails to process devices that are specified on the command line.
[Test Case]
* Actual
$ df -h /dev/sda1
Filesystem Size Used Avail Use% Mounted on
udev 1.8G 8.0K 1.8G 1% /dev
* Expected
$ df -h /dev/sda1
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 9.9G 978M 8.5G 11% /
[Regression Potential]
* This patch is a partial backport of functions as they exist in vivid to help minimize the regression potential.
* That being said I had to do some backporting so as to avoid ui changes.
* This once again significantly changes the mount search and matching
logic within df, but it is localized to df.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
-------
It appears that the latest version of coreutils uploaded to trusty-updates has a regression in it. We have scripting that checks how much space we have left on a partition using `df /dev/sda1`. Using coreutils 8.21-1ubuntu5.1, we can do the following:
$ df -h /dev/sda1
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 9.9G 978M 8.5G 11% /
This is a valid way of using the tool per the manpage: "If an argument is the absolute file name of a disk device node containing a mounted file system, df shows the space available on that file system rather than on the file system containing the device node"
It appears that either 8.21-1ubuntu5.2 or 8.21-1ubuntu5.3 broke this, however. We now get output for the udev filesystem that is mounted at /dev, instead of the device we pass in.
$ df -h /dev/sda1
Filesystem Size Used Avail Use% Mounted on
udev 1.8G 8.0K 1.8G 1% /dev
This is both a behaviour change, and contravenes the manpage, so it would be good to get this fixed.
Changed in coreutils (Ubuntu): | |
assignee: | nobody → Dave Chiluk (chiluk) |
Changed in coreutils (Ubuntu Trusty): | |
assignee: | nobody → Dave Chiluk (chiluk) |
tags: | added: regression-update sts |
Changed in coreutils (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in coreutils (Ubuntu): | |
milestone: | none → trusty-updates |
Changed in coreutils (Ubuntu Trusty): | |
milestone: | none → trusty-updates |
Changed in coreutils (Ubuntu): | |
milestone: | trusty-updates → none |
Changed in coreutils (Ubuntu): | |
status: | Confirmed → Invalid |
description: | updated |
Changed in initramfs-tools (Ubuntu Trusty): | |
status: | New → Confirmed |
assignee: | nobody → Dave Chiluk (chiluk) |
Changed in initramfs-tools (Ubuntu): | |
status: | New → Invalid |
Changed in initramfs-tools (Ubuntu Trusty): | |
importance: | Undecided → Critical |
importance: | Critical → Medium |
Changed in coreutils (Ubuntu Trusty): | |
status: | Confirmed → Triaged |
no longer affects: | coreutils (Ubuntu) |
no longer affects: | initramfs-tools (Ubuntu) |
Changed in initramfs-tools (Ubuntu Trusty): | |
status: | Confirmed → Triaged |
Changed in coreutils (Ubuntu Trusty): | |
status: | Triaged → In Progress |
Changed in initramfs-tools (Ubuntu Trusty): | |
status: | Triaged → In Progress |
tags: |
added: verification-done removed: verification-needed |
tags: |
added: verification-done-initramfs removed: verification-done |
tags: |
added: trusty removed: verification-done-initramfs |
Ack thanks for the bug.
Verified incorrect behavior exists in trusty, xenial is not experiencing the issue though. I will take a closer look tomorrow when I'm back from vacation.