I keep my music collection on a NAS that is connected to the network using NFS.
It has worked perfectly well with Amarok 1.4/MySQL, during more than a year.
Not so with 2.x, though (2.1.1 at the moment).
No problem if I shut the computer running 2.x down; it will pick up where it left off.
But if the NAS is down (or disconnected from the lan) while the other computer starts up, no such luck. Amarok will only scan local directories - not the collection on the network. Update won't help; I have to rescan the whole collection.
1.4 works perfectly, it just waits until the NAS is up.
Is this a well-known bug in Amarok 2.x/MySql, or is it it something to do with my distro (Mandriva Cooker)?

I have the same problem with Amarok 2.1 on an opensuse 11.1 box connected to a NAS with my whole music collection, so the problem is not connected to your distribution.

My NAS gets mounted during the boot process by a crontab entry (see the section FAQ: Tricks for a Slow Network) at http://opensuse.swerdna.org/susesambacifs.html (written for CIFS/Samba but also works for NFS), but still it will not recognize the collection on the NAS without a total rescan. I guess this depends on the location of the Amarok collection database file.

So for me too - any help appreciated..

tarp wrote:I have the same problem with Amarok 2.1 on an opensuse 11.1 box connected to a NAS with my whole music collection, so the problem is not connected to your distribution.

My NAS gets mounted during the boot process by a crontab entry (see the section FAQ: Tricks for a Slow Network) at http://opensuse.swerdna.org/susesambacifs.html (written for CIFS/Samba but also works for NFS), but still it will not recognize the collection on the NAS without a total rescan. I guess this depends on the location of the Amarok collection database file.

So for me too - any help appreciated..

First try 2.1.1.
I assume you have a fstab entry not a crontab entry for mounting your NAS via NFS
So the NAS will be mounted by whom, root?
Plz. Post the line in your fstab.
Is the mountpoint present, when you start amarok?
Does A2 start the scan by itself or initiated through you?

m0nk

I use Amarok 2.1.1.
I mount my NAS by fstab:

10.0.0.2:/c/media /mnt/media nfs rw,hard,intr 0 0

I assume that the NAS is mounted as user, since I can read, write and edit the files on the drive as user (according to user privilegies defined in the NAS setup)

The crontab entry makes the NAS present when starting up Amarok. I have to initiate the collection scan.

Tarp

I really don't understand the crontab entry. Either your NAS is mounted at boot time by fstab entry or not. There's no need for a crontab entry. And you shouldn't mount a NFS share hard, but soft and bg.
Is /mnt/media selected in your Amarok setup for watched folders?
Is /mnt/media/ present in your amarokrc under [Collection Folders]?

m0nk

I use the crontab entry to run the mount command delayed so that the (slow) wireless network is up.

"And you shouldn't mount a NFS share hard, but soft and bg" - I will change that to see if it makes any difference.

/mnt/media is selected in my Amarok setup for watched folders and /mnt/media/ is present in my amarokrc under [Collection Folders]

- Tarp