Red Hat Bugzilla – Bug 183960
SQL Dumps Library when NFS server is offline
Last modified: 2008-09-14 10:58:46 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060223 Fedora/1.5.0.1-5 Firefox/1.5.0.1 Description of problem: I'm running Amarok on my machine and 2 kids machines via NFS to a main server. If I'm working on that server and it's offline, the entire (local) music library dumps and has to be rebuilt once the server is up again. The main SQL database seems to still have all the applicable album art, lyrics, etc, yet rebuilding the library at the local level with a 6000+ song library takes 20-30 minutes on a fast machine, and 45 minutes to an hour on older hardware. I don't want to disable "watch folders for changes" in setup for obvious reasons. There needs to be a warning message pop-up that says, "music library not found. Rebuild or cancel." Yes this probably needs to go the the Amarok Dev people at a feature request. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. 2. 3. Additional info:
What version of amarok was the OP using? Amarok 1.4.2+ is supposed to have a feature called a "dynamic collection" (http://amarok.kde.org/wiki/Dynamic_Collection) that detects if a share is SMB, CIFS, or NFS and doesn't touch files in the library if that collection is unavailable. Unfortunately this feature doesn't appear to be working, or is poorly explained on the wiki page. I have a problem where I have one music store at home that I access via CIFS share and one at work also accessed via a CIFS share. When I startup amarok at either of these locations my collection is completely erased and it rebuilds for the new share. My understanding of the feature is that this shouldn't happen.
Sometime after 1.4.4 (probably 1.4.5) CIFS support will be added. See my forum post here: http://amarok.kde.org/forum/index.php/topic,13201.0.html
This does look like it should be reported upstream. After doing so please update this report with the upstream info.
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping