Weirdness with ATF and Collection Scanner
Rich
rich at hq.vsaa.lv
Wed Oct 24 07:48:58 UTC 2007
On 2007.10.24. 06:35, Greg Meyer wrote:
> I have been playing around a bit with my database to replace some tracks with
> higher quality versions without losing the stats, and it is going well,
> except for some weirdness.
>
> My music is located on an NFS share, and it is deviceid 7 in my database. My
> root filesystem, is defined as deviceid 32. The NFS share is mounted
> at /mnt/music.
which amarok version ? device id 32 is pretty huge, especially for a
root fs...
if you don't have the latest version, you should upgrade and do a full
rescan. if you have, it might help to see devices table contents.
> I am noticing that I can rescan the collection, and sometimes all the tracks
> come in on deviceid 7 with a path of ./blahblah and another time after a
> rescan they show up with deviceid 32 and a path of /mnt/music/blahblah.
>
> This doesn't seem to be a problem, as ATF is picking up the uniqueid properly
> and transferring the stats. Do you guys think this is benign or a sign of a
> potential problem, perhaps one that manifests itself by losing stats when ATF
> is forced off in the config file.
--
Rich
More information about the Amarok
mailing list