[prev in list] [next in list] [prev in thread] [next in thread] 

List:       amarok-bugs-dist
Subject:    [amarok] [Bug 328543] Autofs mounted network drive disconnection forces collection re-indexation.
From:       <mathieu.beliveau.1 () gmail ! com>
Date:       2013-12-13 14:52:08
Message-ID: bug-328543-71684-BBVnj9NphN () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=328543

--- Comment #11 from mathieu.beliveau.1@gmail.com ---
I did some more testing with autofs, and it seems Solid does add an entry after
I've been trying to access the share:

With autofs on, using the --ghost option, when accessing the share via dolphin,
the following entry is added to solid-hardware list details:

udi = '/org/kde/fstab///192.168.1.150/share/'
  parent = '/org/kde/fstab'  (string)
  vendor = 'share/'  (string)
  product = '192.168.1.150'  (string)
  description = 'share/ on 192.168.1.150'  (string)
  StorageAccess.accessible = true  (bool)
  StorageAccess.filePath = '/home/strav/nas/share'  (string)
  StorageAccess.ignored = false  (bool)
  NetworkShare.type = 'Cifs'  (0x2)  (enum)
  NetworkShare.url = 'smb://192.168.1.150/share/'  (string)

With autofs off (when trying to access the mounted root folder or not) it does
not appears.

Now without the --ghost option, I'm getting somewhat inconsistent behaviours:

- If autofs is on and I succeeded in accessing the share, the Solid entry 
(udi = '/org/kde/fstab///192.168.1.150/share/') is consistently listed whether
or not I am accessing the mounted folder. 

- If autofs is on while I'm disconnected, the udi =
'/org/kde/fstab///192.168.1.150/share/ entry still shows up in solid-hardware
list details (with:  StorageAccess.accessible = true)  while accessing the
mounted location hangs Dolphin in a very nasty way (killall -9 dolphin is
barely effective). 

Note that this sort of behaviour on faulty mounted network location is the
reason I use autofs with --ghost in the first place. 

In the end, I really ain't sure if the actual collection re-scanning problem
with autofs mounted share really is a Solid issue. 

Thanks for keeping me updated on this!

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Amarok-bugs-dist mailing list
Amarok-bugs-dist@kde.org
https://mail.kde.org/mailman/listinfo/amarok-bugs-dist
[prev in list] [next in list] [prev in thread] [next in thread]