From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: utf-8' chars from Winxp machine may be problem related (was Re: xfs file system in process of becoming corrupt; though xfs_repair...)
Date: Wed, 07 Jul 2010 18:40:21 -0500 [thread overview]
Message-ID: <4C351065.7060803@hardwarefreak.com> (raw)
In-Reply-To: <4C34F464.6060506@tlinx.org>
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@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-07-07 23:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-27 1:10 WARNING xfsdump [still] Cannot allocate memory for list of [root|non-root] attributes for nondir ino xxyz Linda A. Walsh
2010-06-28 2:27 ` Dave Chinner
2010-06-29 22:33 ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ; -/ (was xfs_dump problem...) Linda Walsh
2010-06-29 23:25 ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ;-/ " Dave Chinner
2010-06-29 23:55 ` Michael Weissenbacher
2010-06-30 0:42 ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ; -/ " Linda A. Walsh
2010-06-30 1:16 ` Dave Chinner
2010-06-30 2:45 ` Linda A. Walsh
2010-07-01 23:58 ` Dave Chinner
2010-07-07 3:18 ` Linda A. Walsh
2010-07-07 5:56 ` Linda Walsh
2010-07-07 6:36 ` Dave Chinner
2010-07-07 9:30 ` Linda A. Walsh
2010-07-07 21:01 ` Linda Walsh
2010-06-30 0:01 ` Linda A. Walsh
2010-06-30 1:06 ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ;-/ " Dave Chinner
2010-06-30 1:52 ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ; -/ " Linda A. Walsh
2010-06-30 21:01 ` Stan Hoeppner
2010-07-07 21:40 ` utf-8' chars from Winxp machine may be problem related (was Re: xfs file system in process of becoming corrupt; though xfs_repair...) Linda A. Walsh
2010-07-07 23:40 ` Stan Hoeppner [this message]
2010-07-08 0:38 ` Linda A. Walsh
2010-06-30 18:25 ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ; -/ (was xfs_dump problem...) Michael Monnerie
2010-06-30 23:30 ` rsync and corrupt inodes (was xfs_dump problem) Dave Chinner
2010-07-01 8:25 ` Michael Monnerie
2010-07-02 2:42 ` Dave Chinner
2010-07-02 6:21 ` Michael Monnerie
2010-07-04 22:53 ` Dave Chinner
2010-07-12 11:28 ` Michael Monnerie
2010-07-07 21:56 ` Linda Walsh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C351065.7060803@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox