Re: Unnecessary hard drive spin-ups

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

 



On 2/12/20 7:09 PM, Roger Heflin wrote:
It may be the pwd command doing it.  It works like this:

if something runs pwd when its cwd is under say /var/log then pwd goes
through all files in /var/log until it finds .. then it goes up a
directory and repeats, until it gets to /.
That makes sense. Just occurred to me: a typical shell prompt displays the cwd, so 'pwd' or something like it must get run just before a shell prompt is displayed. This likely explains why I'd sometimes experience the spin-up delay after running a command: it wasn't the command itself necessarily that triggered the spin-up but the pwd afterwards.
Assuming that is the case your solution would be expected to work,
It seemed to work earlier today when I fired up the green USB hard drive in that I experienced no spin-up delays, but...

  if you put it under /mnt/backups then any other pwd anywhere under mnt
may also cause the spinup.  On nfs mounts an nfs mount that is hanging
of say /mnt/host1 can hang everything else in /mnt even coming from
other responding hosts.  the trick there is to
/mnt/host1/host1mntpoint and put each separate host in a separate top
level directory to isolate them from each other.  You may not need to
do that so long as you don't have other things in /mnt being used that
may cause a pwd.
That's a great idea. I've gone ahead and implemented it on my PCs.
if you run ls -l /proc/*/cwd | more it will show you everything
running's cwd.  I see /var/spool/at (atd process) with that as a home
dir, so atd doing a pwd would cause a spinup.

I don't actively use atd for anything and strace does not show atd
doing anything on my machine.  If you use atd then it may be what is
doing it. nfs's statd also its cwd under var and is used on nfs
servers.

There certainly are a lot of processes on my PC running cwd. Interesting...

Thanks!
Dave
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
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