Bug 725201 - [ext4/xfstests 204] fails of ENOSPC blocking tests on small filesystem
Summary: [ext4/xfstests 204] fails of ENOSPC blocking tests on small filesystem
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.1
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: 6.6
Assignee: Lukáš Czerner
QA Contact: Filesystem QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-24 04:15 UTC by Eryu Guan
Modified: 2014-05-19 13:16 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-19 13:16:02 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Eryu Guan 2011-07-24 04:15:14 UTC 
Description of problem:
xfstests 204 fails on ext4 with 'No space left on device'

Version-Release number of selected component (if applicable):
kernel-2.6.32-131.0.15.el6

How reproducible:
Unknown, I think it's below 10%

Steps to Reproduce:
1. install xfstests
2. check 204
3.
  
Actual results:
+./204: line 53: echo: write error: No space left on device
+./204: line 53: echo: write error: No space left on device
+./204: line 53: echo: write error: No space left on device
...

Expected results:
Pass test

Additional info:
A failure log on ppc64

http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2011/07/1141/114180/234194/2532603/12455804//test_log--kernel-filesystems-xfs-xfstests-204.log

https://beaker.engineering.redhat.com/recipes/234194

fail on rhel5 ext4 see bug 720876
fail on rhel5 xfs see bug 660638
Comment 2 RHEL Program Management 2011-10-07 15:42:11 UTC 
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Note You need to log in before you can comment on or make changes to this bug.