Your message dated Sun, 18 Dec 2016 03:26:12 +0100
with message-id <[email protected]>
and subject line Re: Bug#779412: block devices loosing state after resume:
trigger udev rules to re-apply settings
has caused the Debian Bug report #779412,
regarding block devices loosing state after resume: trigger udev rules to
re-apply settings
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
779412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779412
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Description follows.
--- End Message ---
--- Begin Message ---
Control: tags -1 + wontfix
On Sat, 28 Feb 2015 09:38:27 +0100 Michael Biebl <[email protected]> wrote:
> Am 28.02.2015 um 09:30 schrieb Chris:
> > (http://bugs.debian.org/779412 explanation)
> >
> > There is a general problem with non-permanent block devices settings
> > (hard disks, optical disks, usb storage, ...), that are not restored
> > when resuming from suspend (instead using factory defaults and
> > loosing all pre-suspend settings).
> >
> > And as long as the ata/scsi command set drivers can not save and
> > restore every state register a device may have (impossible?),
> > systemd may ship a viable workaround for this:
> >
> > A systemd unit file could trigger an udev change action upon resume for
> > block devices. This way the same udev rules that set up the devices when
> > they are first plugged, will re-apply their settings after resume.
> >
> > Providing this centrally with the systemd package could avoid that
> > multiple packages ship their own files, resulting in multiple change
> > events triggerd on each resume.
> >
> > Examples for very important (non-permanent) settings are with
> > hdparm (i.e. the important -B hard disk wear settings)
> > https://bugs.debian.org/725284
> > smartctl/mdadm/lvm/btrfs/zfs/... (i.e. set error recovery timeouts to
> > prevent controller resets and data loss)
> > http://sourceforge.net/p/smartmontools/mailman/message/33501936/
> >
>
> I don't think working around this in udev/systemd is a good idea.
> After all, most of those custom settings aren't applied via udev rules
> anyway. This should be fixed in the kernel properly (or the individual
> services) and not be papered over in systemd.
>
I'm still pretty much convinced that we should not do that
unconditionally in udev.
Thus closing the bug report as wontfix
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
