files on a shared (smb) device remain in "missing files" even when device becomes available again
Submitted by Jim Nelson
Link to original bug (#717061)
Description
---- Reported by jim@yorba.org 2010-11-09 12:24:00 -0800 ----
Original Redmine bug id: 2787
Original URL: http://redmine.yorba.org/issues/2787
Searchable id: yorba-bug-2787
Original author: Jim Nelson
Original description:
Originally reported at:
https://bugs.launchpad.net/bugs/673049
Binary package hint: shotwell
Folders and files on the shared device are visible in nautilus.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: shotwell 0.7.2-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Tue Nov 9 !15 (merged):08:00 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
PATH=(custom, user)%(=caps)LANG%=it_IT.utf8SHELL=/bin/bash
SourcePackage: shotwell
Related issues:
- related to shotwell - 2857: Files imported across a soft link can go offline and neve... (Invalid)
- related to shotwell - 4834: Cannot use NFS share as library (Open)
- related to shotwell - 5764: can't use SMB share as library via .gvfs (Open)
- duplicated by shotwell - 4133: Unreliable access to photos on samba share (Duplicate)
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-16 14:35:00 -0700 ----
History
Comment 1
Updated by Jim Nelson about 3 years ago
It's possible this is a duplicate of #2857 (closed).
Comment 2
Updated by Mike Lococo over 2 years ago
Confirming that I'm affected by this or something similar as well. I haven't found a reliable way to reproduce, but when I've observed it goes something like:
-
Import images, manage collection, tag stuff, normal shotwell use.
-
Shut shotwell down.
-
Start shotwell, some images are listed as missing files.
-
Confirm that the mount is active, check the file-location via “Extended Informationâ€. Confirm that the file is available and viewable in gthumb.
-
Restart shotwell, 3-4 of the times this has happened the files are found and shotwell recovers gracefully.
-
Manage collection, tag stuff, normal shotwell use.
-
One image that has been edited externally and has a modified version is shown as missing it's file. Check the mount, check the original file and the modified version with gthumb, both are available.
-
Restart shotwell, this time it doesn't resync.
-
Remove the photo from the DB, and re-import. Re-modify with the external- editor.
- Note that there is not necessarily a time when shotwell observed these files as offline. I mount my smb-share via fstab on boot, although I do often access the files over a wireless network which makes the storage performance fairly slow. Perhaps there's a timeout being triggered somewhere.
- Note that not all the collection is affected, only some apparently random subset.
So far this hasn't caused any catastrophic problems, but it does make one nervous. In the case where it didn't resync automatically, I had to re-import and lost all shotwell-specific data like versions and event-names.
Comment 3
Updated by Jim Nelson about 2 years ago
- Description updated (diff)
Comment 4
Updated by Mike Lococo about 2 years ago
I've just updated to 0.11.2 and can confirm that a variant of this bug, or a similar bug still exists. It's been quite some time since I experienced the problem described in steps 7, 8, and 9 of comment 2 where an image edited using an external editor is permanently marked as missing. Perhaps this was a one-off issue or has been fixed inadvertantly in another changeset.
However, the issue described in 3, 4, 5 now happens nearly every time I run shotwell. Resummarizing my circumstances:
-
Shotwell is run on a laptop with fairly limited local storage. The .shotwell directory and it's associated DB are stored on this local storage.
-
The photo directory is set to ~/Pictures in shotwell. This is a symlink pointing to an smbmount in /media/mountpoint which is automatically mounted at boot via fstab. This photo directory is not shared with any other user, or accessed by any other automated photo organizer. The storage is remote for capacity reasons only.
-
The server is Samba 3.5.8 running on Ubuntu 11.04. The network interconnect is gigabit ethernet (at one time I would occasionally use wireless, but given the problems I've observed with shotwell I now never start the application unless I'm at my desk and connected via ethernet). The disk throughput of this remote mount has been measured to be comparable to a USB-connected hard-disk (20-50MB/sec). I haven't tested latency, though I suspect it might be a bit worse than a USB-disk. I can test this if necessary. The salient point is that it's a fairly performant home-server, and these issues aren't caused by substantial IO delays related to poor server performance.
-
When shotwell is started, you can see the "items" count in the basic- information panel start counting up at about 100 items per second as shotwell does some kind of startup checking. During this period, the "Missing Files" icon appears in the left-panel beneath the Trash icon.
-
Much of the time, the item-count reaches the actual number of items in the collection within a moment or so (I currently have ~12k photos and less than 50 short videos in my collection) and the "missing Files" icon disappears as expected.
-
Normal shotwell use: view, tag, etc.
-
At some point the "Missing Files" icon reappears with a random number of items in it. Sometimes 100 photos, other times as many as 4000 photos are shown as missing their files. Other files in the same mountpoint are available, checking the purportedly missing files in nautilus or with a file- based photo viewer like gthumb shows that they are actually available. It's unknown what if any user-action triggers the files to be detected as missing. The "missing files" icon is often scrolled off the bottom of the left-panel, so I only notice it when scrolling down to check on it.
-
Restart shotwell and repeat from step 4. Generally the photos come back online for a while, and then go away again. It's hard to tell if there's a pattern as to which photos go offline. It's not a clear and simple pattern, but it may be that the oldest photos are most prone to going missing... or maybe I just notice them more often because they're at the top of the list.
Comment 5
Updated by Mike Lococo about 2 years ago
- Description updated (diff)
Reconfirming as described in comment 4. Now with:
- Shotwell 0.11.4, running on Ubuntu 11.10.
- Samba 3.5.11 in Ubuntu 11.10.
I understand that 0.11.6 should be landing in the Onieric repos soon. I'll test again then, but this represents a major OS rev on both the client and server with no change in behavior... as well as several shotwell revs.
Comment 6
Updated by Jim Nelson 12 months ago
- Priority changed from Low to High
- Target version set to 0.14.0
Comment 7
Updated by Jim Nelson 11 months ago
- Category set to library-mode
Comment 8
Updated by Jim Nelson 11 months ago
- Category changed from library-mode to network-storage
Comment 9
Updated by Jim Nelson 11 months ago
- Target version changed from 0.14.0 to 0.15.0
Comment 10
Updated by Jim Nelson 6 months ago
-
Target version deleted (
<strike>
_0.15.0_</strike>
)
--- Bug imported by chaz@yorba.org 2013-11-25 21:48 UTC ---
This bug was previously known as bug 2787 at http://redmine.yorba.org/show_bug.cgi?id=2787
Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one. Resolution set on an open status. Dropping resolution