[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: UTF-8 problem with NTFS support?



More strangeness. A person who knows what is on the disk says there
are no strange filenames, just ordinary letters and numbers, so the
utf-8 stuff seems like a red herring. Maybe something is corrupt? Ran
ntfsck:

ntfsck  /dev/sdc1
Unsupported: replay_log()
Unsupported: check_volume()
Checking 45024 MFT records.
Unsupported cases found.

Googled that, still confused. Apparently, ntfsck does not actually do
anything about replay_log or check_volume yet? So it's not clear what
it does or doesn't do, or whether this disk is OK or DOA.

Am I missing something? How can I troubleshoot this filesystem?

mahalo,
Dave

On Mon, Mar 23, 2009 at 11:25 AM, Dave Burns <tburns hawaii edu> wrote:
> I've mounted an external USB hard drive on my fc-10 system. I have all
> teh NTFS-3G packages installed.
>  rpm -qa|grep -i NTFS
> ntfs-3g-2009.2.1-2.fc10.x86_64
> ntfs-3g-devel-2009.2.1-2.fc10.x86_64
> ntfsprogs-2.0.0-9.fc10.x86_64
> ntfsprogs-devel-2.0.0-9.fc10.x86_64
> ntfsprogs-gnomevfs-2.0.0-9.fc10.x86_64
>
> One directory seems to cause a problem:
>
> ls /MyBook/paleo_enso/solar_forcing
> ls: reading directory /MyBook/paleo_enso/solar_forcing: Invalid or
> incomplete multibyte or wide character
>
>
> Find apparently gives up entirely, returns nothing where I know there
> is something:
>  find /MyBook/paleo_enso/solar_forcing
> /MyBook/paleo_enso/solar_forcing
>
>
> Also, this appears in the log:
> grep -i ntfs /var/log/messages
> Mar 23 08:03:41 c ntfs-3g[3165]: Incomplete multi-sector transfer:
> Input/output error
> Mar 23 08:03:41 c ntfs-3g[3165]: Skipping unrepresentable filename
> (inode 34473): Invalid or incomplete multibyte or wide character
> Mar 23 08:03:43 c ntfs-3g[3165]: Incomplete multi-sector transfer:
> Input/output error
> Mar 23 08:03:43 c ntfs-3g[3165]: Skipping unrepresentable filename
> (inode 34473): Invalid or incomplete multibyte or wide character
>
> Googling all that leads me to a bug that was supposed to be fixed(? I
> think? bug is 'version 9', mine is ntfs-3g-2009.2.1-2):
> https://bugzilla.redhat.com/show_bug.cgi?id=467629
>
> http://www.ntfs-3g.org/support.html#utf8b says to make sure UTF-8 is
> okay, I think it is:
> [root c ~]# env|grep LANG
> LANG=en_US.utf8
>
> But there's obviously something here I don't understand. Can anyone
> point me in the right direction?
>
> The only workaround I can think of is somehow using the inode and
> mv/renaming the bogus files. But I don't know how to use mv with only
> an inode number (man page a bit terse).
>
>
> thanks,
> Dave
>



-- 
———————————————————————-
Q: Why should this email be 5 sentences or less?
A: http://five.sentenc.es
IPRC-help FAQ: https://wailua/wiki/index.php/Faq


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]