On Tue, 25 Aug 2015 00:28:37 +0100, TJ wrote:
I've followed the issue with interest. Glad you finally identified the
cause.
I wonder if smartd ought to be taught to check the power/sleep state
of a device and only query it if it is currently awake/active?
I don't know if this is possible and
PS:
Don't get me wrong.
jackd does not wake up green drives, I only mentioned it to demonstrate
that by installing a package, it possible to interact with the user.
I don't have all those gnomeish file managers installed for my Wily
install, neither K3b and the KDE archive manager are
Update:
1.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484497/comments/6
2.
Running ps aux I found /usr/sbin/smartd -n.
[weremouse@moonstudio ~]$ man smartd
[snip] smartd will attempt to enable SMART monitoring on ATA
devices (equivalent to smartctl -s on) and polls these
Smartd documents -n by itself as no-fork (normal for systemd/upstarted
stuff) but you also need to configure nocheck whichconfusingly is
documented as -n POWERMODE -- man smartd for more on possible
POWERMODE values.I do not know if the manual is inaccurate as I
have NOT checked, just
On Mon, 24 Aug 2015 08:59:37 -0700, Michael Loftis wrote:
On Mon, Aug 24, 2015 at 6:30 AM, Ralf Mardorf wrote:
To be continued...
Smartd documents -n by itself as no-fork (normal for systemd/upstarted
stuff) but you also need to configure nocheck whichconfusingly is
documented as -n POWERMODE
On 24/08/15 18:11, Ralf Mardorf wrote:
I've followed the issue with interest. Glad you finally identified the cause.
I wonder if smartd ought to be taught to check the power/sleep state of a
device and only query it if it is currently awake/active?
--
Ubuntu-devel-discuss mailing list
Update:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484497/comments/4
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484497/comments/5
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
Hi Ralf,
Maybe you could help me clarify something from your experience: in my
case, since the disk I'm talking about is the system disk (root
partition) it is almost impossible to have it go to sleep, right? I
mean, there will always be some writes from time to time.
This is basically a
On Thu, 20 Aug 2015 00:40:55 +0100, João M. S. Silva wrote:
Maybe you could help me clarify something from your experience: in my
case, since the disk I'm talking about is the system disk (root
partition) it is almost impossible to have it go to sleep, right?
I don't know.
Assumed that even an
On 08/14/2015 10:07 PM, Ralf Mardorf wrote:
On Sat, 15 Aug 2015 01:33:46 +0100, João M. S. Silva wrote:
On 08/15/2015 01:12 AM, Ralf Mardorf wrote:
As already pointed out, the drive in question is _sdc_, not _sdb_
What about kworker?
I wonder, if AppArmor or any of the other software I
On Mon, 17 Aug 2015 08:47:33 -0500, Jamie Strandboge wrote:
On 08/14/2015 10:07 PM, Ralf Mardorf wrote:
On Sat, 15 Aug 2015 01:33:46 +0100, João M. S. Silva wrote:
On 08/15/2015 01:12 AM, Ralf Mardorf wrote:
As already pointed out, the drive in question is _sdc_, not _sdb_
What about
On 08/13/2015 10:20 PM, Ralf Mardorf wrote:
Write frequency :
4 systemd-journal
10 kworker/u8:2
45 kworker/u8:1
60 kworker/u8:0
128 jbd2/sdb11-8
If jbd2 is writing 12.8 times per min how can your disk spin down after
30 min?
Even if you increase jdb2 sync like
On Sat, 15 Aug 2015 00:57:42 +0100, João M. S. Silva wrote:
If jbd2 is writing 12.8 times per min how can your disk spin down
after 30 min?
As already pointed out, the drive in question is _sdc_, not _sdb_ [1].
Regards,
Ralf
[1]
On Thu, 13 Aug 2015 23:20:25 +0200, Ralf Mardorf wrote:
[snip]
A
On 08/15/2015 01:12 AM, Ralf Mardorf wrote:
As already pointed out, the drive in question is _sdc_, not _sdb_ [1].
What about kworker?
--
João M. S. Silva
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
On Sat, 15 Aug 2015 01:33:46 +0100, João M. S. Silva wrote:
On 08/15/2015 01:12 AM, Ralf Mardorf wrote:
As already pointed out, the drive in question is _sdc_, not _sdb_
What about kworker?
I wonder, if AppArmor or any of the other software I didn't chose to
install myself could be the
On Thu, 13 Aug 2015 12:09:47 +0200, I wrote:
To be continued...
There's no need to run smartctl again. I sit side by side to the green
drive and without gvfs, libfm, lxpanel, udisks2, spacefm, rodent
packages installed, something waked up the green drive. I didn't start
any Qt or KDE based
Hi,
sorry for cross-posting, but there's quasi no traffic at
Ubuntu devel discuss, so I hope somebody subscribed to
Ubuntu Studio devel has got an idea, how to find the culprit.
A few days ago I tried to fix an issue cause by lxpanel, respl. by a
dependency of it, libfm. This issue is fixed by
Any ideas how to file a bug against unknown buggy software, or perhaps
a bad unknown Ubuntu specific configuration?
A bug report is useless, since I don't know what package does cause the
issue.
:D
Begin forwarded message:
Date: Thu, 13 Aug 2015 12:26:25 -
From: Ubuntu Foundations Team
I'm not sure if I understood your issue correctly, but I also have a
server with a mechanical disk which periodically spins, don't know why.
There are tools like powertop or so, but I guess you already tried that.
I think I also did and it didn't help.
Maybe try Linux (kernel) IRC channel?
On 13/08/15 11:09, Ralf Mardorf wrote:
Hi,
Something still wakes up green drives.
Any hints to catch the culprit are welcome.
I believe this is a known issue with WD Green drives. There are a few
workarounds for this, for example:
https://forum.manjaro.org/index.php?topic=17890
I tried lm-monitor on my server and got:
Write frequency :
35 kworker/u2:0
40 kworker/u2:2
57 kworker/u2:1
137 jbd2/sdb1-8
Read frequency :
1 dhclient-script
1 dirname
1 ip
From the suggestions for service disabling I could only follow the
advice to disable
Thank you,
unfortunately it doesn't help.
On Thu, 13 Aug 2015 14:12:23 +0100, João M. S. Silva wrote:
I'm not sure if I understood your issue correctly, but I also have a
server with a mechanical disk which periodically spins, don't know why.
There are tools like powertop or so, but I guess
Thank you for your reply,
a lot of people trying to help me guess I need to fix my green WD
drive. The drive is ok, does exactly what it should do and what it must
do regarding an EU Regulation for external drives.
It does not happen for Linux in general.
It happens for my Ubuntu install, not
On Thu, 13 Aug 2015 13:39:05 +, Michael Bejer-Andersen wrote:
Have you looked into
lm-profiler(http://linux.die.net/man/8/lm-profiler) to hopefully catch
what is waking up the drive?
No, I didn't. Thank you, I now have laptop-mode-tools + 29 dependency
packages installed. Btw. it's a tower
With option commit=50 in the ext4 partitions I was able to reduce jbd2
IO frequency. But the disk keeps spinning on/off with a frequency of
around 10 s.
So jdb2 (which was also a problem for Arch Linux users, saw it in a post
from 2011) is not the culprit.
On 08/13/2015 02:47 PM, Ralf
On Thu, 13 Aug 2015 13:11:54 -0700, Michael Loftis wrote:
Maybe try a little harder to ID the process causing the wakeup? Have
you tried looking for blocked processes at the moment you hear the
drive start to spin up? Look for processes in D state at the time the
drive is spinning up.
Thank
Maybe try a little harder to ID the process causing the wakeup? Have
you tried looking for blocked processes at the moment you hear the
drive start to spin up? Look for processes in D state at the time the
drive is spinning up.
On Thu, Aug 13, 2015 at 6:47 AM, Ralf Mardorf
On Thu, 13 Aug 2015 19:47:28 +0100, João M. S. Silva wrote:
With option commit=50 in the ext4 partitions I was able to reduce jbd2
IO frequency. But the disk keeps spinning on/off with a frequency of
around 10 s.
So jdb2 (which was also a problem for Arch Linux users, saw it in a
post from
28 matches
Mail list logo
