 Bill_MIBill In MichiganPremium,MVM
join:2001-01-03
Royal Oak, MI
kudos:1
 ·WOW Internet and..
·Comcast
| reply to robman50
Re: mounting a share at boot Many have been through the boot problem but I think recent distros have tweaked many things in the interest of "user-friendly". Anyone confirm or deny?
Robman50, I do suggest taking a good look at filenames - especially any with funny characters in them from Windows. If you have none or very few, it may be no issue but could bite you in the future. It's what the "iocharset=utf8" option is all about.
Just my 2 cents. Good Luck! |
|
| said by Bill_MI:Robman50, I do suggest taking a good look at filenames - especially any with funny characters in them from Windows. If you have none or very few, it may be no issue but could bite you in the future. It's what the "iocharset=utf8" option is all about.
Just my 2 cents. Good Luck!
The file system of the share is FAT32 and it is correctly displaying the long file names. So I guess it's working good.  |
|
Bill_MIBill In MichiganPremium,MVM
join:2001-01-03
Royal Oak, MI
kudos:1 Reviews:
·WOW Internet and..
·Comcast
| It's not long filenames. It's extended characters Windows can have in filenames. Like this stuff... ¡¢£¤¥¦§¨¨ª«¬®¯ a0-af °±²³´µ¶·¸¹º»¼½¾¿ b0-bf ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏ c0-cf ÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞß d0-df àáâãäåæçèéêëìíîï e0-ef ðñòóôõö÷øùúûüýþÿ f0-ff ĀāĂ㥹ĆćĈĉĊċČčĎď 100-10f ĐđĒēĔĕĖėĘęĚěĜĝĞğ 110-11f I wonder how that's displaying to everyone. What can happen is you'll have a file that you can do NOTHING with, including deleting it. |
|
|
|
| I had that happen to me with an text file from a DOS game once. |
|
 MaxoYour tax dollars at work.Premium,VIP
join:2002-11-04
Tallahassee, FL | reply to Bill_MI
I'm currently sharing some media from my server to my XBMC machine over SMB and running into this exact problem. Files named "Star Wars Episode IV: A New Hope.iso" show up something like "STAR~WA~1.ISO" or something horrible like that. |
|
Bill_MIBill In MichiganPremium,MVM
join:2001-01-03
Royal Oak, MI
kudos:1 Reviews:
·WOW Internet and..
·Comcast
| Hi Maxo, Your example sounds more like a long filename problem but you might give the iocharset=utf8 a try.
I wish I were more versed in this (anyone?). But I do recall old DSLR links on a Windows machine having bullet and vertical line characters that blew Nautilus' mind until I did that. |
|
davePremium,MVM
join:2000-05-04
not in ohio
kudos:8 | The wire protocol encodes strings as Unicode, specifically UTF16-LE (ok, you can use a byte-oriented character set for some SMBs but you really don't want to, it's old-crap mode).
Your client software is responsible for converting to and from whatever representation is in use on the client machine. For the cifs vfs, this is done with the iocharset option.
(For the old and crap smbfs, you'll need to manually make sure the client multibyte character set matches the so-called OEM character set on the server; you really don't want to. Unicode, the only sane way to represent characters since 1990).
Regardless of the above, the following are not legal filename characters in Windows. Blame DOS.
* ? < > | :
4 of those are wildcards, 1 is meaningless but illegal, and 1 is a valid separator between filename and streamname, which really will confuse your semantics.
»kernel.org/doc/readme/fs-cifs-README |
|
MaxoYour tax dollars at work.Premium,VIP
join:2002-11-04
Tallahassee, FL | reply to Bill_MI
The SMB client in this case is XBMC. My long term solution will be to switch to NFS. I wish XBMC supported SSH/SFTP. |
|
davePremium,MVM
join:2000-05-04
not in ohio
kudos:8 | I just noticed the colon in your example. The cifsvfs has ways to preserve the not-legal-in-Windows characters by mapping them into the Unicode 'private use' range going to the server, and back again coming from the server. Maybe your client does to (if it uses its own SMB implementation rather than the kernel file system).
This will likely 'display funny' on clients that don't have the same option configured, but the client's round-trip fidelity will be preserved. |
|
MaxoYour tax dollars at work.Premium,VIP
join:2002-11-04
Tallahassee, FL | Perhaps I should file a bug report with XBMC. |
|
 BranoI hate VogonsPremium,MVM
join:2002-06-25
Burlington, ON
kudos:6
 ·Bell Fibe
| reply to Maxo
said by Maxo:I'm currently sharing some media from my server to my XBMC machine over SMB and running into this exact problem. Files named "Star Wars Episode IV: A New Hope.iso" show up something like "STAR~WA~1.ISO" or something horrible like that.
What is the server you're sharing from running for OS? |
|
MaxoYour tax dollars at work.Premium,VIP
join:2002-11-04
Tallahassee, FL | Ubuntu 12.04 server. |
|
BranoI hate VogonsPremium,MVM
join:2002-06-25
Burlington, ON
kudos:6 Reviews:
·Bell Fibe
| I'm not 100% sure, but I'm leaning towards saying that the problem lies within the server and not client.
I have QNAP NAS here with linux guts (samba as server) and am mounting shares on Win7 and openSUSE and Mint. All long names are appearing fine. However (while ago) I had openSUSE server with samba server and the long filenames were giving me the FOO~1.ext problem. That's why I'm thinking it depends how the server is configured (no real proof though). |
|
Bill_MIBill In MichiganPremium,MVM
join:2001-01-03
Royal Oak, MI
kudos:1 Reviews:
·WOW Internet and..
·Comcast
| reply to Maxo
said by Maxo:The SMB client in this case is XBMC. My long term solution will be to switch to NFS. I wish XBMC supported SSH/SFTP. How's the same share look on a Linux or Windows client?
I also wonder what the original fs is on that share? I'm sharing some ext4 partitions from Ubuntu Server 10.04 and it's been 100% trouble free when I fstab/manually mount with iocharset=utf8. Or on a Windows box, though XP is the latest I've tried. No XBMC to test. |
|
MaxoYour tax dollars at work.Premium,VIP
join:2002-11-04
Tallahassee, FL | All my machines are running Ubuntu 12.04 with an ext4 filesystem. If I get around to it I'll trying viewing the shares from another Ubuntu machine in Nautilus over SMB. |
|
MaxoYour tax dollars at work.Premium,VIP
join:2002-11-04
Tallahassee, FL | reply to Bill_MI
Yep, it looks messed up in Nautilus too. |
|
Bill_MIBill In MichiganPremium,MVM
join:2001-01-03
Royal Oak, MI
kudos:1 Reviews:
·WOW Internet and..
·Comcast
| Interesting. Notice it's coming up with the old MSDOS 8x3 including all upper case and that ~x uniqueness portion. Yet MSDOS always used numeric AFAIK. This points more towards the server and not the client.
It would be interesting to locate the character(s) involved. As dave pointed out, the colon: is one good guess.
Nautilus plays some tricks (I curse the handling of *.desktop files). You might take a look at filenames from a terminal at the fuse mount. It hides in a hidden directory in your home directory: ~/.gvfs/. I'll guess they will look just like nautilus.
EDIT: I tried naming a file "Star Wars Episode IV: A New Hope.iso" on an ext4 cifs share but no problem with it. |
|
MaxoYour tax dollars at work.Premium,VIP
join:2002-11-04
Tallahassee, FL | Yes, it shows up the same way under bash.
david@heorot:~/.gvfs/video on 192.168.2.10/Movies$ ls -l *~*
-rwx------ 1 david david 4601262080 Feb 4 2012 B4J988~8.ISO
-rwx------ 1 david david 3506905088 Feb 4 2012 E619I4~G.ISO
-rwx------ 1 david david 4550443008 Feb 1 2012 HLPGKG~5.ISO
-rwx------ 1 david david 4159262720 Feb 5 2012 L5PC5H~4.ISO
-rwx------ 1 david david 4154535936 Feb 5 2012 LJ0UUD~M.ISO
-rwx------ 1 david david 5130729472 Feb 5 2012 LWBFBN~V.ISO
-rwx------ 1 david david 4612560896 Feb 2 2012 RH4XQG~H.ISO
-rwx------ 1 david david 4110014464 Feb 3 2012 S020YW~X.ISO
-rwx------ 1 david david 4594675712 Feb 2 2012 S3EAXC~D.ISO
-rwx------ 1 david david 4614938624 Feb 2 2012 S489QG~K.ISO
-rwx------ 1 david david 2196021248 Feb 5 2012 S7FP9M~C.ISO
-rwx------ 1 david david 4577794048 Feb 2 2012 S89NM2~L.ISO
-rwx------ 1 david david 4603811840 Feb 3 2012 S9BNV9~Z.ISO
-rwx------ 1 david david 4568260608 Feb 3 2012 SCTWD4~F.ISO
-rwx------ 1 david david 4561199104 Feb 2 2012 SFSJNG~X.ISO
-rwx------ 1 david david 4615798784 Feb 2 2012 SGMIGK~8.ISO
-rwx------ 1 david david 4279611392 Feb 3 2012 SK001Y~Q.ISO
-rwx------ 1 david david 4602324992 Feb 3 2012 SPZHFP~R.ISO
-rwx------ 1 david david 4585365504 Feb 3 2012 ST393T~L.ISO
-rwx------ 1 david david 4600604672 Feb 3 2012 ST5HVK~7.ISO
-rwx------ 1 david david 4342693888 Feb 2 2012 STFZDY~8.ISO
-rwx------ 1 david david 4614453248 Feb 3 2012 STG92R~P.ISO
-rwx------ 1 david david 4610529280 Feb 2 2012 SUIP0M~T.ISO
-rwx------ 1 david david 4608522240 Feb 2 2012 SVCNTQ~4.ISO
-rwx------ 1 david david 4598906880 Feb 3 2012 SWLS68~K.ISO
-rwx------ 1 david david 4608299008 Feb 4 2012 TCFC2G~Y.ISO
-rwx------ 1 david david 4599994368 Feb 4 2012 TJCZPN~4.ISO
-rwx------ 1 david david 4502611968 Feb 5 2012 TJMYFI~2.ISO
-rwx------ 1 david david 4560734208 Feb 4 2012 TJWY15~B.ISO
--
"Padre, nobody said war was fun now bowl!" - Sherman T Potter
»maxolasersquad.com/
»maxolasersquad.blogspot.com
»www.facebook.com/maxolasersquad |
|
Bill_MIBill In MichiganPremium,MVM
join:2001-01-03
Royal Oak, MI
kudos:1 Reviews:
·WOW Internet and..
·Comcast
| I would probably be on the serving box, moving or copying a few of those to a separate directory to start playing with filenames while observing the share names. Ubuntu 12.04 server. A few thoughts...
When you're in a shell, use bash to TAB complete a filename. Note the escaped characters. It might reveal some hints (like why is that "u" escaped?... it's not a regular "u"!).
Star Wars Episode IV: A New Hope.iso
Should be as expected...
Star\ Wars\ Episode\ IV\:\ A\ New\ Hope.iso
Here's hoping a light comes on! |
|
davePremium,MVM
join:2000-05-04
not in ohio
kudos:8 | reply to robman50
Taking a Wireshark trace while you create a file named "foo:bar" would quickly tell you who was mangling the names. Maybe
echo >/mountpoint/foo:bar
ls /mountpoint
so you can then see if the name was reported 'wrongly' even if created correctly.
(If you want to send the trace to me I'll take a look) |
|
