| Summary: | disk flush utilize cpu to 100% and freeze system after copying large file | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Ondřej Šibřina <sibrina> |
| Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | xmw |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
kernel .config
dmesg hdparm -I /dev/sda hdparm -tT /dev/sda lspci lsusb |
||
|
Description
Ondřej Šibřina
2010-06-08 20:55:11 UTC
Created attachment 234589 [details]
kernel .config
Created attachment 234591 [details]
dmesg
Created attachment 234593 [details]
hdparm -I /dev/sda
Created attachment 234595 [details]
hdparm -tT /dev/sda
Created attachment 234601 [details]
lspci
Created attachment 234603 [details]
lsusb
Hello Ondřej, have you tried to confirm the health of you RAM? Install sys-apps/memtest86+ and boot into it, run the normal test sets for some hours and hopefullz there's no error. Michael p.s. do you see SATA relatet errors on the kernels log? Run `dmesg` and watch for rediscoveries of you dist. You can stress test the disks connection by installing tools like sys-block/buffer and run `buffer -i /dev/sda -o /dev/null -z 512k` and see the data rate. If it's low, try to debug the link by using another cable, clean the connections ... Michael Dear Michael, thank you for interest. I tried memtest and i got not error after 5 passed. I don't think it's memory problem because there's no crashes. Then i tried buffer `buffer -i /dev/sda -o /dev/null -z 512k` you suggest. I get result like 100000K/s constatly. During test my CPU was 60% (10% buffer process, 50% wait) and my computer wasn't stuck. I can't see any errors in my dmesg while flushing ;-( I'm not sure but it looks like connection works good. Don't you think? Thank you for future steps. Ondrej (In reply to comment #9) > I tried memtest and i got not error after 5 passed. I don't think it's memory > problem because there's no crashes. ok > Then i tried buffer `buffer -i /dev/sda -o /dev/null -z 512k` you suggest. I > get result like 100000K/s constatly. During test my CPU was 60% (10% buffer > process, 50% wait) and my computer wasn't stuck. this is ok, one processor is constntly waiting for the process in iowait state, which results in 50% (1 of 2 cpus) utilization. > I'm not sure but it looks like connection works good. Don't you think? Yes. The starange thing is the relativley low average write speed of 20MB/s (5 seconds "freeze" for approx. 100MB) and that it affects both your cpu cores. One in waiting would be ok (other non io-wait processes would still be ran on this) and the other should be just free. I looked up you IO_SCHED settings, nothing wrong with that. I just saw the SDD, can you please check if you partitions have strange boundaries which do not allign to the internal data format of the SDD (bug 320655)? But that would only lead to a bad write speed, not a frozen desktop. You're using a ZEN kernel, is this the the host or the guest? Have you tried another kernel, like the stable gentoo-sources or just any LiveCD/DVD image? Can you erase the disk or an partition? Would be nice to see if a non-destructive write test with badblocks lead to the same problem. If not, bonnie is the choice for write tests. Can you try these with another kernel? Michael Hi, which kernel sources do you use? sys-kernel/zen-sources? which version? Michael Dear Micheal, I'm sorry for late response, but I had bachalor final exams, so i had another point to think about. Actually i have kernel from zen-sources linux-2.6.33-zen2.I started with gentoo-sources 2.6.34 and then try kernel from zen sources to solve my problem but it doesn't work. It's not possible (too complicated) to erase my partition. It's system partition and i haven't disc to store my data. I'll try run some live-distribution CD and mount my partition with that and let you know it'll work. I'll add emerge --info file in attachment. Thank you for help Ondrej Sibrina |
