ubuntu_zram_smoke_test will generate a huge output file and choking jenkins
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| ubuntu-kernel-tests |
High
|
Colin Ian King |
Bug Description
[~/test-
$ du -sh * |grep G
1.5G ms10-34-
6.2G ms10-35-
[~/test-
$ du -sh * |grep G
6.2G ubuntu_
[~/test-
$ du -sh *
512 lost+found
6.2G test
Changed in ubuntu-kernel-tests: | |
importance: | Undecided → High |
Changed in ubuntu-kernel-tests: | |
assignee: | nobody → Colin Ian King (colin-king) |
status: | New → In Progress |
Colin Ian King (colin-king) wrote : | #1 |
Colin Ian King (colin-king) wrote : | #2 |
Ah, I see the issue, it's not being umounted for some weird reason. I can debug and fix this now I can see why it's an issue.
Colin Ian King (colin-king) wrote : | #3 |
sudo umount /dev/zram0
umount: /home/ubuntu/
..so the umount is failing, hence leaving the file system populated with a large file that consumes memory. Sigh.
Colin Ian King (colin-king) wrote : | #4 |
We have a kernel thread blocked,
root 2880 2 0 08:31 ? 00:00:00 [jbd2/zram0-8] .. and I can't umount the file system.
Colin Ian King (colin-king) wrote : | #5 |
09:00:26 ERROR| [stderr] + sync
09:07:58 INFO | Timer expired (1200 sec.), nuking pid 3106
OK - so it looks like the test was being killed and it's not cleaned up properly.
Colin Ian King (colin-king) wrote : | #6 |
Fix sent, should be committed by EOD
Colin Ian King (colin-king) wrote : | #7 |
@Sam, is this now working OK? If so, can we close this bug?
Po-Hsu Lin (cypressyew) wrote : | #8 |
Hi Colin,
the patch was not accepted yet.
Colin Ian King (colin-king) wrote : | #9 |
Colin Ian King (colin-king) wrote : | #10 |
Based on Sam's reply:
<PHLin> cking, the zram test looks good
..I'm marking this as fixed.
Changed in ubuntu-kernel-tests: | |
status: | In Progress → Fix Released |
FYI, ~/test- results/ 4.4.0-132. 158~14. 04.1-generic/ ms10-35- mcdivittB0- kernel_ _4.4.0- 132.158~ 14.04.1_ _2018-08- 03_23-53- 00/ubuntu_ zram_smoke_ test/results/ ubuntu_ zram_smoke_ test.zram- smoke-test/ mnt is mounted on /dev/zram0 and is on a memory based zram file system.
The test will populate the file system on /dev/zram0. Is the test crashing or timing out?