linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris <email.bug@arcor.de>
To: Michael Biebl <biebl@debian.org>
Cc: linux-raid@vger.kernel.org, 725284@bugs.debian.org,
	smartmontools-support@lists.sourceforge.net,
	779412@bugs.debian.org
Subject: Re: Bug#779412: block devices loosing state after resume: trigger udev rules to re-apply settings
Date: Sat, 28 Feb 2015 10:47:44 +0100	[thread overview]
Message-ID: <20150228104744.45c8d5b0@smtp.arcor.de> (raw)
In-Reply-To: <54F17E83.5070400@debian.org>

Am Sat, 28 Feb 2015 09:38:27 +0100
schrieb Michael Biebl <biebl@debian.org>:

> I don't think working around this in udev/systemd is a good idea.

Idealy and in the long run, the kernel drivers should keep state, yes.
But until then, better not to make releases with default configurations
that deliver serious problems (excessive hardware wear, data loss) to
the users. 

I believe before things stadardized around systemd and udev, packages
like hdparm, laptop-mode-tools, pm-utils, acpi-support,
gnome-power-manager, and more, all tried to work around problems with
block devices loosing state. Unfortunately, accumulating a large mess
and interferences resuling in releases with many bugs in this regard.

Now the situation can improve a lot, if we can say packages are safe if
they use udev rules to initialize devices. (As the kernel keeps
state, or systemd centrally triggers a udev change event where this is
not (yet) the case.)

> most of those custom settings aren't applied via udev rules
> anyway.

Which settings were you refering to?
With current versions hdparm, mdadm, etc. all seem to ship udev rules.
And that seems to be the proper way to configure the standard
hot-pluggable systems of today. (leaving aside embedded, non-systemd,
non udev systems)



------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/

      reply	other threads:[~2015-02-28  9:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-28  8:30 block devices loosing state after resume: trigger udev rules to re-apply settings Chris
2015-02-28  8:38 ` Bug#725284: Bug#779412: " Michael Biebl
2015-02-28  9:47   ` Chris [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150228104744.45c8d5b0@smtp.arcor.de \
    --to=email.bug@arcor.de \
    --cc=725284@bugs.debian.org \
    --cc=779412@bugs.debian.org \
    --cc=biebl@debian.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=smartmontools-support@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).