@JoseCRodriguez: "Hi
I have set my hard drive to standby after a given time through laptop-
mode. The hd actually passes to standby mode but only for half a
second or so after which it spins up again. If I issue hdparm -y /dev/
hda the same behaviour is observed.
I checked the logs inmediatly after this happens but found nothing
meaningful to me. As far as I can tell I have configured syslog.conf
in a way that log daemons will not sync after each minor event. I
deactivated some daemons to check whether they could be the cause
(lpd, cron, hal)  but the problem persists.
Is there a way to track down what is accessing the drive? I found a
program called blktrace which seems to be useful in this situation,
but I'd like to hear from any other suggestions.
System is running sid with 2.6.23 custom kernel.
Thanks
To UNSUBSCRIBE, email to <email_address> 
with a subject of "unsubscribe". Trouble? Contact <email_address>"
    @dtutty: "<quote>
You may need something like noflushd.  Don't know if its on sid.  When
activated, it keeps the filesystem from syncing to disk unnecessarily.
Doug.
To UNSUBSCRIBE, email to <email_address> 
with a subject of "unsubscribe". Trouble? Contact <email_address>"
    @JoseCRodriguez: "<quote>
Hi, thanks for the reply. I solved it following the directions found
in the laptop-mode website FAQ:
echo 1 > /proc/sys/vm/block_dump
which enables checking disk activity through dmesg. It turned out that
I hadn't put the "-" sign before EVERY log file name in /etc/
syslog.conf...
I took a look at noflushd, but apparently it can't handle journaling
file systems for they bypass the kernel's delayed write mechanism (*).
Oh, well, it works now anyway.
Thanks!
(*) <url>
To UNSUBSCRIBE, email to <email_address> 
with a subject of "unsubscribe". Trouble? Contact <email_address>"
{'source': 'USENET', 'other_information': '{"reply_count": 2, "forum_name": "linux.debian.user.20141229.mbox"}', 'file': 'data/output/usenet-linux.debian.parquet'}