xattr test in ubuntu_stress_smoke_test failed on 4.8 i386 Yakkety
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
Bug Description
Kernel: 4.8.0-40.43 i386 Yakkety
Test case "xattr" in ubuntu_
I don't think I've seen this in previous SRU cycles.
xattr FAILED
stress-ng: debug: [31101] 6 processors online, 6 processors configured
stress-ng: info: [31101] dispatching hogs: 4 xattr
stress-ng: info: [31101] cache allocate: default cache size: 8192K
stress-ng: debug: [31101] starting stressors
stress-ng: debug: [31102] stress-ng-xattr: started [31102] (instance 0)
stress-ng: debug: [31103] stress-ng-xattr: started [31103] (instance 1)
stress-ng: debug: [31101] 4 stressors spawned
stress-ng: debug: [31104] stress-ng-xattr: started [31104] (instance 2)
stress-ng: debug: [31105] stress-ng-xattr: started [31105] (instance 3)
stress-ng: fail: [31105] stress-ng-xattr: fsetxattr failed, errno=117 (Structure needs cleaning)
stress-ng: debug: [31105] stress-ng-xattr: exited [31105] (instance 3)
stress-ng: fail: [31104] stress-ng-xattr: fsetxattr failed, errno=117 (Structure needs cleaning)
stress-ng: debug: [31104] stress-ng-xattr: exited [31104] (instance 2)
stress-ng: debug: [31102] stress-ng-xattr: exited [31102] (instance 0)
stress-ng: debug: [31101] process [31102] terminated
stress-ng: debug: [31103] stress-ng-xattr: exited [31103] (instance 1)
stress-ng: debug: [31101] process [31103] terminated
stress-ng: error: [31101] process 31104 (stress-ng-xattr) terminated with an error, exit status=1
stress-ng: debug: [31101] process [31104] terminated
stress-ng: error: [31101] process 31105 (stress-ng-xattr) terminated with an error, exit status=1
stress-ng: debug: [31101] process [31105] terminated
stress-ng: info: [31101] unsuccessful run completed in 10.02s
Full log: http://
| description: | updated |
| Brad Figg (brad-figg) wrote Missing required logs. | #1 |
| Changed in linux (Ubuntu): | |
| status: | New → Incomplete |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1669697
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.