HDD standby interrupted

adrhc · 01-19-2018, 08:19 AM

Quote:

Originally Posted by norobro

Take a look in the following two files and see if any files on your mounted drive are listed. On my system there are several old files listed that I have since deleted. I think because of the change in gedit 3.20 the drive isn't accessed.

Code:

$ grep recently strace-gedit.log 
open("/home/gigi/.local/share/recently-used.xbel", O_RDONLY) = 14
open("/home/gigi/.local/share/recently-used.xbel.PUQDDZ", O_RDWR|O_CREAT|O_EXCL, 0666) = 15

You might try moving those files out of the way and running gedit to see if your drive still spins up.

Hm, I found the below in /home/gigi/.local/share/recently-used.xbel:

Code:

  <bookmark href="file:///mnt/1TB/Temp/Adila/info.txt" added="2017-12-22T14:15:11Z" modified="2017-12-22T14:45:31Z" visited="2017-12-22T14:15:11Z">
    <info>
      <metadata owner="http://freedesktop.org">
        <mime:mime-type type="text/plain"/>
        <bookmark:groups>
          <bookmark:group>gedit</bookmark:group>
        </bookmark:groups>
        <bookmark:applications>
          <bookmark:application name="gedit" exec="&apos;gedit %u&apos;" modified="2017-12-22T14:45:31Z" count="11"/>
        </bookmark:applications>
      </metadata>
    </info>
  </bookmark>

Additionally Visual Studio Code also use that file:

Code:

open("/home/adr/.local/share/recently-used.xbel", O_RDONLY) = 119

It contains the /mnt/1TB path - could this be the problem?

rknichols · 01-19-2018, 12:19 PM

Note: I had not yet seen the immediately above post when I wrote this. (The page breaks in this forum sometimes come at unfortunate places.)

Still nothing apparent. Perhaps a child process is involved. Try adding "-f" to the strace options and see if anything turns up. You don't need to attach all these huge files. Just see if the path to the mount point shows up in the trace. If not, the only other thing I can think of is that gedit does have some dbus interactions, and perhaps one of those is triggering the disk access. I don't know how to look for that.

adrhc · 01-19-2018, 01:53 PM

Thank you guys. I removed

Code:

<bookmark href="file:///mnt/1TB/Temp/Adila/info.txt" ...

from /home/gigi/.local/share/recently-used.xbel and for the moment gedit seems to no longer interrupt the HDD sleeping. Anyway in order for this to be considered the solution (the removal of any bookmarks pointing to sleeping HDD) I'll have to wait this night to pass - so the computer to rest untouched few hours - and after it to test again with strace and gedit.

Considering OpenDocumentSelector: fix fetching of recents (see previous @norobro post) I guess gedit reads the last access time for all the recent opened files (listed in recently-used.xbel) which is hitting all HDDs on which they are stored. The gedit fix doesn't seems to me to solve my particular problem - what do you think?

@rknichols
Maybe

Code:

open("/var/lib/dbus/machine-id", O_RDONLY) = 14

rknichols · 01-19-2018, 02:27 PM

Quote:

Originally Posted by adrhc

@rknichols
Maybe

Code:

open("/var/lib/dbus/machine-id", O_RDONLY) = 14

Not likely. All that can be done from there is to read the 128-bit machine ID for the local system (32 hex characters). No disk access involved.

adrhc · 01-20-2018, 01:45 AM

I run again:

Code:

strace -e trace=file -o $HOME/strace-file-gedit.log gedit

and again the HDD sleeping was interrupted (I attached the last part of the log).

Nothing found here (e.g. /mnt/1TB):

Code:

grep -i mnt .local/share/recently-used.xbel

or here:

Code:

grep -i mnt strace-file-gedit.log

The removal of /mnt/1TB references from recently-used.xbel doesn't seems to be the solution.

adrhc · 01-20-2018, 02:07 AM

With some bash tricks I also learned that there are not referentes to /mnt from the files listed in strace-file-gedit.log attached above:

Code:

grep '("/' strace-file-gedit.log | grep -v 'No such file or directory' | cut -f2 -d'"' | uniq | sort > files.txt
while read -r line; do if [ -f "$line" ]; then grep -i mnt $line; fi done < files.txt

adrhc · 01-21-2018, 02:14 AM

I run again the strace test:

Code:

strace -e trace=file -o $HOME/strace-file-gedit.log gedit

and I attached exactly only the strace lines (337) outputted when pressing the Open button in gedit.