H.S. wrote at 2009-05-28 17:38 -0600:
> I have two hard disks (IDE) on my Testing machine. The main one that I
> use is hda. I have some partitions on hdb. I use noflushd to spin hdb
> down when it is not in use. However, I have noticed recently that the
> disk spins up immediately af
Hello,
I have two hard disks (IDE) on my Testing machine. The main one that I
use is hda. I have some partitions on hdb. I use noflushd to spin hdb
down when it is not in use. However, I have noticed recently that the
disk spins up immediately after noflushd spins it down. I see these in
syslog
Hello,
this is my first post here. I use Debian unstable on my fanless VIA
EPIA home workstation. Noise is a big deal for me, so I use noflushd to
spin down the HD. However log-messages spin it up, especially dhclient.
I have tried adding "-" chars in /etc/syslog.conf but it keeps s
I've noticed recently that if noflushd is started while a USB flash
drive is present noflushd will try and spin down /dev/sda (the flash
drive) and ignore /dev/hda.
on these occations "/etc/init.d/noflushd start" says:
Starting No Flush Daemon: pdflush wakeup interval 0 s
sk is EXT3 I won't get very far :-). I'll
look into hdparm, thanks for the suggestion.
I have realised what the problem was regarding it not printing out
messages -- in Woody, I had produced my own command line in the
/det/defaults/noflushd file and this included the verbose switch. When
On Mon, Aug 16, 2004 at 11:19:29PM +0100, Matthew T. Atkinson wrote:
> 'ello,
>
> I'm pretty sure that noflushd is not spinning down /dev/hdd after 5 mins
> (which is how I have it set up). Unfortunately, no messages from it are
> appearing in syslog (they used to in
On Monday 16 August 2004 16:19, Matthew T. Atkinson wrote:
> 'ello,
>
> I'm pretty sure that noflushd is not spinning down /dev/hdd after 5 mins
> (which is how I have it set up). Unfortunately, no messages from it are
> appearing in syslog (they used to in Woody) so I am
'ello,
I'm pretty sure that noflushd is not spinning down /dev/hdd after 5 mins
(which is how I have it set up). Unfortunately, no messages from it are
appearing in syslog (they used to in Woody) so I am unable to tell
exactly what isn't working.
Has anyone else had these proble
f
> the box, caching-only).
FWIW, I have a very similar box as my wireless access point and dialup
machine. With noflushd, I typically keep the disk spun down for 24 hours
at a time.
> ls -rt indicates that syslogd & al. are responsible for the
> frequent activity, at any rate
reports 30-40MB (out of 80) not even to be used for
buffering. Now, I thought there is a way to force the machine
to fill it's buffers until either a) the disk's up anyway or b) it
runs out of memory. Furthermore, I thought noflushd would be
taking care of this.
the command used: nofl
l either a) the disk's up anyway or b) it runs
out of memory. Furthermore, I thought noflushd would be
taking care of this.
the command used: noflushd -n15 /dev/hda
trying to check it with -vd, I get the following: Error: no valid
timeout for /dev/hda
Now I wonder what I'm doing wro
l either a) the disk's up anyway or b) it runs out of
memory.
Furthermore, I thought noflushd would be taking care of this.
the command used:
noflushd -n15 /dev/hda
trying to check it with -vd, I get the following:
Error: no valid timeout for /dev/hda
Now I wonder what I'm doing wro
Krzys Majewski wrote:
> This the potato sysklogd and a noflushd compiled from the
> sources in woody.
> Presumably the problem is noflushd logging a "Spinning
> down..." message, which gets flushed to the hard drive, heh.
> Now, I've prefixed all the file
Noflushd spins the disk up immediately after spinning it
down, unless I do a etc/init.d/sysklogd stop.
This the potato sysklogd and a noflushd compiled from the
sources in woody.
Presumably the problem is noflushd logging a "Spinning
down..." message, which gets flushed to the hard
14 matches
Mail list logo