I just noticed this seems to be the same problem as mentioned in the
"Problems with yesterday CVS and international characters"-thread which
I failed to find before sending "my problem" to the list.
Are you sure that XFS can't have to do with this? (What baffles me is
how this can avoid affecting ext2, and clearly depends on whether I use
2.4.16-xfs or 2.4.17-xfs (I change obsolutely nothing else between my
tests) if it is not XFS-related.)
Best regards,
Håkan Lindqvist
On Sun, 2002-01-27 at 04:23, Håkan Lindqvist wrote:
> The current (as of today) CVS version of linux-2.4-xfs (2.4.17) does not
> seem to be able to handle files created under earlier versions of XFS
> which have filenames containing certain (latin1) characters (Swedish
> characters å,ä,ö (a with ring on top, a with dots on top and o with dots
> on top) for example).
>
> The kind of errors I get is that if I run ls so that it finds these
> files it spits out "ls: <filename>: No such file or directory" (the
> filename can be a match of a wildcard or tabcompletion - so it can't be
> a case of bad typing).
> Going back to my previous kernel (2.4.16-xfs) makes things work again.
> However if I create a new file with a å (for example) in the filename
> under 2.4.17-xfs, that file causes the same kind of problem under
> 2.4.16-xfs.
>
> It seems that stat:ing the file fails eventhough the file exists and can
> be found. (This output from "strace ls -l janneååå" seems to point in
> that direction too: 'lstat64("janneååå", 0x80548bc) = -1 ENOENT
> (No such file or directory)')
>
> This does not seem to affect other filesystems (at least not ext2),
> therefore I assume the issue is with some new XFS code.
>
>
> Best regards,
> Håkan Lindqvist
>
>
|