Bug 1142459

Summary: No obvious errors show when root partion runs out of space
Product: [Fedora] Fedora Reporter: Adrian Likins <alikins>
Component: cockpitAssignee: Patrick Uiterwijk <puiterwijk>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: puiterwijk, stefw
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cockpit-0.26-1.fc21 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-16 02:09:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
journalctl -b-o export output none

Description Adrian Likins 2014-09-16 19:43:15 UTC 
Created attachment 938214 [details]
journalctl -b-o export output

Description of problem:

If all the space on / (/dev/mapper/fedora-root) is used
nothing in the web ui shows any warning, even when on the
"storage" page. 

(say, after creating 15 100m loop devices https://bugzilla.redhat.com/show_bug.cgi?id=1142443)

After switching pages to the journal, I did eventually get the red 'oops'.

Looking at console, there are kernel messages logged about being unable to write to loop devices, various other errors, and then journal and auditd shuts down.


Version-Release number of selected component (if applicable):
Version 0.23.
Built on Wed Sep 10 13:43:38 UTC 2014.

How reproducible:
Haven't attempted to reproduce yet, but I suspect something like:
- download the fedora docker image
- start a shell, yum update it
- create a bunch of 100m files and losetup them ala https://bugzilla.redhat.com/show_bug.cgi?id=1142443



Actual results:

Console errors, and errors in journalctl, but nothing in
storage journal on storage detail page, and no alerts or warnings.

Expected results:

Warnings or errors when the drive ran out of space. I think attempting
to format the created raid device did it. 

Additional info:

System is still running after deleting disk images and detaching loop devices

journalctl -b -o export output attached for the curious.
Comment 1 Stef Walter 2014-09-18 13:41:42 UTC 
Upstream bug: https://github.com/cockpit-project/cockpit/issues/67
Comment 2 Fedora Update System 2014-10-08 08:39:26 UTC 
cockpit-0.26-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/cockpit-0.26-1.fc21
Comment 3 Fedora Update System 2014-10-10 15:58:22 UTC 
Package cockpit-0.26-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing cockpit-0.26-1.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-12464/cockpit-0.26-1.fc21
then log in and leave karma (feedback).
Comment 4 Fedora Update System 2014-10-16 02:09:37 UTC 
cockpit-0.26-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.