samba - Apr 2018 - Samba 4 - ISO-8859-15 filenames not listed while browsing

Thanks for your reply.



> Can you add a step that runs iconv over the generated
> filenames that converts them to utf-8 ?
>

Indeed my choices are limited as I don't have the hand on the application,
and the devs won't hear anything, so adding a conversion step would not be
possible. I know the problem come from that, but my hands are tied.


The problem was always there, it's just that it was 'masked' before,
and
the customer is used to filenames not displaying correctly, but obviously
missing files is more of a problem.


If not, setting unix charset = iso-8859-15 works, as
> you've found, but smbd must convert the characters.
I doubt that is making your access slow though, as
> filename conversion is pretty fast and not usually
> something affecting the fast-path.
>
Is there a way for me to pinpoint where the slowness issue can come from?
Or tune some parameters that might help in this matter?
I can clearly see the difference in performance between setting the 'unix
charset' to 'iso8859' and leaving it to its default 'utf8'
value.


I was hoping to find a way for the samba4 server to behave like samba3 (as
in ignoring bad characters and replacing them with an underscore
character), which in the end resulted in the best compromise.

Any advices are welcomed.
Thank you for your time and help.

Regards.

On Tue, Apr 24, 2018 at 07:24:57PM +0000, Ali SIMON
wrote:
> Thanks for your reply. 
> 
> 
> 
> 
> 
>     Can you add a step that runs iconv over the generated
>     filenames that converts them to utf-8 ?
> 
> 
> 
> Indeed my choices are limited as I don't have the hand on the
application, and
> the devs won't hear anything, so adding a conversion step would not be
> possible. I know the problem come from that, but my hands are tied. 
>  
> 
> The problem was always there, it's just that it was 'masked'
before, and the
> customer is used to filenames not displaying correctly, but obviously
missing
> files is more of a problem. 
> 
> 
> 
>     If not, setting unix charset = iso-8859-15 works, as
>     you've found, but smbd must convert the characters.
> 
>     I doubt that is making your access slow though, as
>     filename conversion is pretty fast and not usually
>     something affecting the fast-path.
> 
> 
> Is there a way for me to pinpoint where the slowness issue can come from?
Or
> tune some parameters that might help in this matter? 
> I can clearly see the difference in performance between setting the
'unix
> charset' to 'iso8859' and leaving it to its default
'utf8' value. 
Use higher level debug numbers with accurate timestamps to
see what the difference between "fast" and "slow" names
are. That's the best advice I can give right now.

Thanks Jeremy,

i'm analyzing this with the application team, we'll see what we can
find.

> I was hoping to find a way for the samba4 server to behave like samba3 (as
> in ignoring bad characters and replacing them with an underscore
> character), which in the end resulted in the best compromise.

In the meantime, do you have any idea why there is difference between the
two version ?
Samba 3 was configured with the default "unix charset = utf-8" and it
was
kind of working, so I'm wondering if this was a "bug" or something
?

Is there any way I can make it behave like before and "silently"
ignore bad
charset ?

Regards