Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 May 2015 22:29:20 +0300
From:      Andrew Nayenko <resver@gmail.com>
To:        Tomek CEDRO <tomek.cedro@gmail.com>
Cc:        "exfat@googlegroups.com" <exfat@googlegroups.com>,  freebsd-bugs@freebsd.org, FreeBSD Filesystems <freebsd-fs@freebsd.org>,  samm@os2.kiev.ua
Subject:   Re: exfatfsck 1.0.1 UTF-8 bug
Message-ID:  <5554F790.6010604@gmail.com>
In-Reply-To: <CAFYkXjm99o=k80_%2BbY0ao3u3HX873%2B8ExGTGsXQQ2gqfQ8desA@mail.gmail.com>
References:  <41f6f1f6-a1c8-4819-af45-f3d291737f63@googlegroups.com>	<5553A92F.4080106@gmail.com> <CAFYkXjm99o=k80_%2BbY0ao3u3HX873%2B8ExGTGsXQQ2gqfQ8desA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
>>> ERROR: `0.indexGroups' real size does not equal to size (237568 !=
>>> 419431).
>>
>> That's the actual problem. This is a USB drive where you've copied the
>> /Application folder under OS X, right? Which OS X version have you been
>> using?
>
> Yes, the drive is USB/Thunderbolt Lacie Rugged 2TB (using USB
> connection), MacOSX Yosemite 10.10.* (hard to tell exactly as several
> computers use it).

I see. I relaxed this check in 1.1, so you just need to upgrade to the 
latest version of fuse-exfat and exfat-utils. Let me know whether they 
work for you.

>>> ERROR: name is too long.
>>> BUG: failed to convert name to UTF-8.
>>
>> I believe this bug was fixed in 1.1. Unfortunately, FreeBSD port is
>> outdated. I've tried to contact the maintainer about a month ago without
>> success.
>
> Yes, I have also noticed that and reported to FreeBSD FS/BUGS mailing
> list and the maintainer. If there is no response I will try to verify
> and prepare an updated version :-)

This would be great! Please keep me informed.

-- 
  Andrew Nayenko <resver@gmail.com>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5554F790.6010604>