Re: Mounting internal disk spins up connected external USB disks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Mar 19, 2019 at 05:41:42PM +1030, Tim via users wrote:
Allegedly, on or about 18 March 2019, Wolfgang Pfeiffer sent:
   Nothing mounted here automatically; the problem is that all disks
that seem to be in reach of the OS and not being fast enough to run
away as fast as they can, get accessed, and then spun up ..

Are there bookmarks to those locations in the file browser?

  Standard here is mc. That friendly file browser never tries to
access stuff, unless i tell the guy to do so ... :) - or at least
that's how I remember it.

Is it checking up on "recently" accessed places?
Do you have the file-browser's sidebar listing other locations?

  If you mean file *chooser*: I just tried it: with udisk2 running
trying to download a file via Firefox does not spin up disks
*currently* - I think I saw different behaviour in the past, where
disks got spun up in such instances.

  But that's not so much my actual problem. What is bothering me much
more is the fact that connected HD's get spun up the moment I try to
mount/unmount only one of them, as long as udisks2, it seems, is
running. And this kills disks, plain and ugly, by running down their
load cycles ..

Again: I solved this issue mostly by issuing
  systemctl stop udisks2

  I already hinted it with a link to the SMART wiki in my last email:
Hard Disks, depending on how they're made, have a limited number of
those cycles: last time I saw somewhere between 300.000 and
600.000. Sometimes 10-20% more of them than the number predicted in
the specs. But I can't rely on these extra cycles: I just try to make
sure disks keep their precious heads down.

  Oh, and I nearly forgot it: This isn't a specific problem with
Fedora, as it seems: I saw some similar behaviour on Debian three or
four months ago. Which is why I'm currently transitioning all my
computers from systemd systems to non-systemd OS's. Not sure whether
this will help, as of yet, sure: but software running down my
hardware, without even giving me a reasonable chance to see what
process is doing this is surely the famous straw on the camel's
back. So yes: Debian, sooner or later, will find its way to the door
here, too.

HTH.

Take care.
Wolfgang
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux