Linda A. Walsh put forth on 7/7/2010 4:40 PM: > So yup...foreign char delight. > > I can easily image most or all of these having been imported from my > winXP machine at > one point -- as I only recently started using Win7. -- and many of the > troublsome japanese > filenames were 'downloaded japanese anime-related stuff' that I did on > my old > XP machine -- which I used as a download client while I did work on my > Win7 machine... > That gave a huge influx of foreign names from a WinXP machine. That > could be what > made the problem jump out so noticeable -- before it was only maybe > 20-30 files out of about a million or more. But in the new batch it was > hundreds out of several thousand, so > they stand out alot more. I run into a similar problem frequently when saving downloads to my XFS samba shares via a Windows client. I don't recall ever seeing XFS corruption, but I do have problems manipulating these file names through bash. Quite often I end up having to rename the files through Windows Explorer to something bash can handle. That usually fixes the problem--not always, but usually. Just for comparison, I'm running: Debian stable (Lenny 5.0.4) rolled 2.6.32.9 from kernel.org, XFS in kernel not as module xfsprogs: 2.9.8-1lenny1 bash: 3.2-4 samba: 3.2.5-4lenny9 W2K and XP Pro clients As I've never seriously dealt with character encoding issues (i.e. changed anything related in Debian), I don't even know where/how to find my servers default character encoding. Google isn't being very friendly here. I'm using whatever character encoding is the default for US English Debian Lenny. -- Stan _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
