SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I just now found a somewhat odd behaviour
of my Linux installation at work... if I write large
files to the hard-drive (either off a nfs-mounted
directory or moving them on the local hard-drive)
the machine seems to lock up for several seconds.
Has anyone ever had such behaviour? it didn't do that
with win2k, but my boxes at home and the notebook
don't seem to have this odd phenomenon. I find it really
annoying, since it delays typing (and display), and the
mouse just freezes in spot while in X.
I'd have thought that a P IV 1.6 could handle that? ;)
Either your system is really low in memory and has to swap even for simple things like moving the mouse around (unlikely), or your chipset / hardware configuration with IDE is causing serious problems. Need more information on the machine you are running on and kernel you are using.
Location: Rome, Italy ; Novi Sad, Srbija; Brisbane, Australia
Distribution: Ubuntu / ITOS2008
If you have a IDE disk why not enable DMA?
hdparm -d 1 /dev/hd? where ? is your drive letter.
THIS CAN POSSIBLY BE DANGEROUS. Make sure your disk can handle it before doing this. I did it once and couldn't boot my system beacause "Drive geometry is out of range" error, so make sure your disk can handle it. I beleive all newer disks should have no problems.
Run hdparm -t /dev/hd? before and after /hdparm -d 1 /dev/hd? to see what a speed increase you'll get!! I got a increase from 15mb/sec to 42mb/sec. Now thats sweet!
Hope that helps
This seems a little odd to me. Changing the hdparm will not affect timing of NFS reads and writes and the problem is reproducable even over a NFS share. Even if you disable DMA mode you still shouldn't notice a delay.
A couple of places to start looking:
Are there any error messages when you type dmesg? You might also try looking in /var/log/messages for anything unusual. Another thing to keep in mind is whether you're using a non-standard filesystem like reiserfs or ext3. These filesystems perform differently and the version you have may contain a bug. It may also have something to do with you're trying to read data from a bad sector on your hard disk in which case you would notice errors in /var/log/messages
Originally posted by griffin Are there any error messages when you type dmesg?
Nope, only one informational message about unknown bridge ressources,
and assuming transparent.
You might also try looking in /var/log/messages for anything unusual.
Looks fine to me, was the first place I was looking, too ;)
Another thing to keep in mind is whether you're using a non-standard filesystem like reiserfs or ext3. These filesystems perform differently and the version you have may contain a bug.
Hmmm ... using Reiser that comes with Slack (or rather 2.4.18). Using that on 4 machines, and only
the workstation at work (the supposedly fastest and best machine) shows this odd behaviour. My old PII-266 notebook on the same network runs smooth.
It may also have something to do with you're trying to read data from a bad sector on your hard disk in which case you would notice errors in /var/log/messages
Possible ... :( I'll read up on hdchecks on Reiser.