mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Grega Fajdiga" <Gregor.Fajdiga@telemach.net>
To: "Anton Altaparmakov" <aia21@cantab.net>, <pkot@bezsensu.pl>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: NTFS errors
Date: Fri, 13 Sep 2002 14:07:57 +0200	[thread overview]
Message-ID: <002e01c25b1e$33a62c30$41448fd5@gregaslo2a75n3> (raw)
In-Reply-To: <5.1.0.14.2.20020913093230.00b1db50@pop.cus.cam.ac.uk>

Good day,

Anton and Pawel thanks for the tip, all is well now.

Best Regards,
Grega
> At 08:35 13/09/02, Grega Fajdiga wrote:
> >Good day,
> >
> >I am using lk 2.4.19 + a NTFS 2.1.0 patch. Once in a while I get
> >lots of these errors:
> >
> >Sep 10 09:24:27 mujo kernel: NTFS-fs error (device 03:01):
> >ntfs_ucstonls(): Unicode name contains characters that cannot be
converted
> >to character set iso8859-1.
> >Sep 12 09:39:29 mujo kernel: NTFS-fs error (device 03:01):
> >ntfs_ucstonls(): Unicode name contains characters that cannot be
converted
> >to character set iso8859-1.
> >Sep 13 09:19:28 mujo kernel: NTFS-fs error (device 03:01):
> >ntfs_ucstonls(): Unicode name contains characters that cannot be
converted
> >to character set iso8859-1.
> >Sep 13 09:20:22 mujo kernel: NTFS-fs error (device 03:01):
> >ntfs_ucstonls(): Unicode name contains characters that cannot be
converted
> >to character set iso8859-1.
> >
> >
> >Are these errors serious? How can I get rid of them?
>
> The errors mean that there are one or more file names containing
characters
> that cannot be displayed with the ISO8859-1 character set. This means that
> you cannot see that those files exist and you cannot access them.
>
> To get rid of the messages and to display the affected file names, you
need
> to use the appropriate character set (which depends on what characters are
> in the file names).
>
> The only character set that can work with all characters is UTF8, so I
> would highly recommend to always use UTF8 and you will never see these
errors.
>
> Best regards,
>
>          Anton
>
>
> --
>    "I haven't lost my mind... it's backed up on tape." - Peter da Silva
> --
> Anton Altaparmakov <aia21 at cantab.net> (replace at with @)
> Linux NTFS Maintainer / IRC: #ntfs on irc.freenode.net
> WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/
>
>


      reply	other threads:[~2002-09-13 12:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-13  7:35 Grega Fajdiga
2002-09-13  8:05 ` Pawel Kot
2002-09-13  8:35 ` Anton Altaparmakov
2002-09-13 12:07   ` Grega Fajdiga [this message]

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='002e01c25b1e$33a62c30$41448fd5@gregaslo2a75n3' \
    --to=gregor.fajdiga@telemach.net \
    --cc=aia21@cantab.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pkot@bezsensu.pl \
    /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

all inboxes | Powered by JetHome®