mounted cifs share failed to ls dir with cyrillic filenames

Bug #585501 reported by Roman Valov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: smbfs

Ubuntu version: Ubuntu 10.04 LTS
Package verison: smbfs 2:3.4.7~dfsg-1ubuntu3
Steps to reproduce:
1) my LANG is ru_RU.utf8, however where is needed I will use en_US for output
2) i have a windows 7 machine with several cifs shares and i wish to mount one of this shares
3) sudo mount -t cifs //server/share /mnt -o user=reddot,uid=reddot
4) when I'm trying to 'ls' dir with cyrrilic filenames, i've got:

reddot@doone:/mnt/frome$ LANG=en_US ls -l
ls: cannot access ?????? ????????? ???????? ? ??? ?????? ?? ????.doc: No such file or directory
ls: cannot access ??????.txt: No such file or directory
total 0
-????????? ? ? ? ? ? ?????? ????????? ???????? ? ??? ?????? ?? ????.doc
-????????? ? ? ? ? ? ??????.txt

By the way, i've no problems in this case with fresh fedora linux.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: I82801AAICH [Intel 82801AA-ICH], device 0: Intel ICH [Intel 82801AA-ICH]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 2272 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801AAICH'/'Intel 82801AA-ICH with STAC9700,83,84 at irq 21'
   Mixer name : 'SigmaTel STAC9700,83,84'
   Components : 'AC97a:83847600'
   Controls : 34
   Simple ctrls : 24
CurrentDmesg:
 [ 70.610992] lp: driver loaded but no devices found
 [ 75.184088] eth0: no IPv6 routers present
 [ 177.504558] Slow work thread pool: Starting up
 [ 177.504652] Slow work thread pool: Ready
DistroRelease: Ubuntu 10.04
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
LiveMediaBuild: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: innotek GmbH VirtualBox
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Regression: No
RelatedPackageVersions: linux-firmware 1.34
Reproducible: Yes
RfKill:

Tags: lucid filesystem needs-upstream-testing
Uname: Linux 2.6.32-21-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

Revision history for this message
Thierry Carrez (ttx) wrote :

Do you manage to see those files when accessing the share through smbclient ?

Changed in samba (Ubuntu):
status: New → Incomplete
Revision history for this message
Roman Valov (reddot) wrote :

Thierry, smbclient correctly displays cyrillic filenames (and generates no errors/warnings) on the same share.

Revision history for this message
Thierry Carrez (ttx) wrote :

Then the issue is probably in the CIFS code in the kernel (or the used mount parameters), and not on samba's side.

affects: samba (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi reddot,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 585501

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Roman Valov (reddot) wrote : AlsaDevices.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Roman Valov (reddot) wrote : ArecordDevices.txt

apport information

Revision history for this message
Roman Valov (reddot) wrote : BootDmesg.txt

apport information

Revision history for this message
Roman Valov (reddot) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Roman Valov (reddot) wrote : Card0.Codecs.codec97.0.ac97.0.0.txt

apport information

Revision history for this message
Roman Valov (reddot) wrote : Card0.Codecs.codec97.0.ac97.0.0.regs.txt

apport information

Revision history for this message
Roman Valov (reddot) wrote : Lspci.txt

apport information

Revision history for this message
Roman Valov (reddot) wrote : PciMultimedia.txt

apport information

Revision history for this message
Roman Valov (reddot) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Roman Valov (reddot) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Roman Valov (reddot) wrote : ProcModules.txt

apport information

Revision history for this message
Roman Valov (reddot) wrote : UdevDb.txt

apport information

Revision history for this message
Roman Valov (reddot) wrote : UdevLog.txt

apport information

Revision history for this message
Roman Valov (reddot) wrote : WifiSyslog.txt

apport information

Revision history for this message
Roman Valov (reddot) wrote :

Hello, Jeremy.
I've reproduced problem on daily-build livecd and problem is still here.

I've also tried upstream kernel.
There is non-permament behaviour. Sometimes inode attributes (permissions, size, etc) are read correctly and 'ls' give no errors. However cyrillic names are still shown with question signs. But sometimes attributes are also failed to be read. I can get pair of these results in sequence of ls commands.

tags: removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → Medium
tags: added: kernel-fs
removed: needs-kernel-logs
Revision history for this message
penalvch (penalvch) wrote :

reddot, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.