Thank You for Your time and answer, Camaleón: >> I have terrible delays/freezes w/ any application whenever HDD (a >> SATA one) does its writing. > >That should not happen at all.
Agree, but... >Consider running a smartctl test on the disk, it can be dying or >having a severe hardware problem. I have run this way: smartctl --test=short /dev/sda in 2 minutes it completed and in its log (-l selftest /dev/sda) I saw its report stating that everything is OK that is no errors found. Seems to me it makes not speed tests but whither an HDD alive, I tried to take long test but it seems to do the same thing just hard way and not performance test... Or I have done something wrong? - I'm new to the utility though. >> My question is, Whether I can make any adjustments as to FS mount >> options, kernel parameters, etc? >> >> The idea is, If it works extremely slow - to reduce its (the writing >> process or whatever related to it) priority or whatever - so it >> affect not the OS almost at all - though the writing will continue >> forever. > >I think you should first find out what makes this (freezes and >slowness) happens because if you're facing a hardware related issue, >there will be no improvements in tweaking the filesystem mount >options, sooner or later your disk will fail and you will only delay >its agony. Well it is my long experience (about 7 years already) w/ SATA HDDs that to me it works slower (on Linux) than the PATA ones - I understand it sounds very weird, but so it is. Long time ago I have seen for example - the SATA HDD w/ less capacity was fsck-ed much longer than PATA one w/ having more capacity - of course there was not heard of / used ext4 at all, ext3 - was the highest version of the FS. And so on. Till this very day I suppose the culprit is the hardware drivers in the kernel or wherever - if it is not so - I mean that a lot of people have high writing/reading speeds of SATAs then I have something to do w/ my configurations :) though I do not have a glue. Having said that I'm not looking for finding a bottle neck w/ the discs, but rather reduce its effect that it has on my systems - at least this is the point that I had when I started the thread. Yet if I'm wrong, and the devices can produce high performance in Linux / Debian, then I would find the problem rather than lowing writing process priority, etc. In this case would You help to investigate the problem? I supply any info relating the matter. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e99a09f.cc88cc0a.48a9.fffff...@mx.google.com
