Bug 135938 - Scan fails with too many errors due to samba file export problems
Summary: Scan fails with too many errors due to samba file export problems
Status: RESOLVED UNMAINTAINED
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 1.4.3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-19 01:28 UTC by Treffer
Modified: 2009-08-02 20:34 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Showing the problematic directory-tree (178.39 KB, image/png)
2006-11-06 17:01 UTC, Christian Nitschkowski
Details
Showing the problematic directory-tree (178.39 KB, image/png)
2006-11-06 17:05 UTC, Christian Nitschkowski
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Treffer 2006-10-19 01:28:38 UTC
Version:           1.4.3 (using KDE KDE 3.5.5)
Installed from:    Ubuntu Packages
Compiler:           ubuntu edgy binary packages, don't know anything about the compiler settings, sorry
OS:                Linux

I've looked at Bug #135243 - This bug is related to these problems, but discribes another way to break the amarok filesystem scan on samba shares. Bug #135243 and dup's were mainly about filesystem permissions, this bug is about filesystem encodings which may produce the same errors but is a different problem - and not yet documented.

My setup:

A Ubuntu drapper server with samba to share a Music library
A Ubuntu edgy client that mounts this share
100MBit network

The client runs amarok to scan the collection. The mp3's on the server contain many utf-8 characters and have partially broken names (? instead of Ä and alike, some scp trouble during data migration).

As soon as I export the filesystem without explicit utf-8 settings in /etc/samba/smb.conf (dos/unix/display charset = ) on the server and /etc/fstab (iocharset=) on the client side the amarok collection scan fails.

Amarok reports files as broken that are either
- completly playable on the client (e.g. with mplayer)
- or not accessable on the client (due to some naming/samba trouble)

I do not know why some accessible files are reported as garbage, and I don't understand why samba exports files which can't be accessed, but it causes amarok to report errors (too many errors).

Please not that these problems are caused by the filesystem encoding and not by fmask/dmask errors. Changing the fs export/import to utf8 solved the problem, so fmask/dmasks were correct. Bug 135243 has a hint for that but does not discribe this scenario. The wiki does not report this problem except for windows 2000/xp (http://amarok.kde.org/wiki/Samba).

It *might* be possible to reproduce this bug using a local samba server/mount, I did not try it, but it might break as well.

Here is my full working fstab entry:

//<ip>/srv-rw                         /mnt/srv        smbfs   username=treffer,password=<pwd>,unhide,rw,user,umask=0770,fmask=0644,dmask=0755,uid=treffer,gid=treffer,iocharset=utf8,noauto      0 0

And the relevant part of smb.conf

[global]
dos charset = UTF-8
unix charset = UTF-8
display charset = UTF-8

Hope you won't kill me for this report...
Comment 1 Christian Nitschkowski 2006-11-06 16:47:40 UTC
I have the same problem.
I've moved my music collection to a samba share last weekend.
When I started amarok, my collection was simply empty (although the paths haven't changed).
All scores I've added to the tracks were gone, too.
When I try to rescan the filesystem, it breaks with too many errors.
All of those reported files contain some Non-ASCII characters.
I'll try to mount the share with UTF-8, too.
Maybe this helps...
Comment 2 Christian Nitschkowski 2006-11-06 16:56:39 UTC
Hmm...
I tried adding the UTF-8 charset to smb.conf on server side.
When I now only scan a few directories and the directory Amarok complained about before, it works just fine.
When I scan my whole collection, it breaks again with the directory it had trouble before.
To make this a little bit clearer, I'll attach a little illustration.
Comment 3 Christian Nitschkowski 2006-11-06 17:01:35 UTC
Created attachment 18435 [details]
Showing the problematic directory-tree

You can see the selected file "06_-_Türkei.mp3"
When I try to scan the whole directory "/home/chrnit/smb4k/APSC01/musik",
Amarok aborts scanning.
It lists the selected file several times and two other files, both have
non-ascii-characters in their names.
When I tell Amarok to only scan "/home/chrnit/smb4k/APSC01/musik/Comedy", it
works just fine.
Comment 4 Christian Nitschkowski 2006-11-06 17:05:03 UTC
Created attachment 18436 [details]
Showing the problematic directory-tree

You can see the selected file "06_-_Türkei.mp3"
When I try to scan the whole directory "/home/chrnit/smb4k/APSC01/musik",
Amarok aborts scanning.
It lists the selected file several times and two other files, both have
non-ascii-characters in their names.
When I tell Amarok to only scan "/home/chrnit/smb4k/APSC01/musik/Comedy", it
works just fine.
Comment 5 Christian Nitschkowski 2006-11-06 17:06:57 UTC
Comment on attachment 18436 [details]
Showing the problematic directory-tree

You can see the selected file "06_-_Türkei.mp3"
When I try to scan the whole directory "/home/chrnit/smb4k/APSC01/musik",
Amarok aborts scanning.
It lists the selected file several times and two other files, both have
non-ascii-characters in their names.
When I tell Amarok to only scan "/home/chrnit/smb4k/APSC01/musik/Comedy", it
works just fine.
Comment 6 Jonas Vejlin 2009-04-04 12:37:10 UTC
is this still the problem with amarok 2?
Comment 7 Myriam Schweingruber 2009-08-02 20:34:16 UTC
Sorry, Amarok 1.4.x is not maintained anymore. The current stable version is Amarok 2.1.1, available in KDE 4.