Date: Fri, 12 Oct 2007 09:49:21 -0400 From: "Bob Johnson" <fbsdlists@gmail.com> To: "Monah Baki" <mbaki@whywire.net> Cc: CyberLeo Kitsana <cyberleo@cyberleo.net>, Bill Moran <wmoran@potentialtech.com>, freebsd-questions@freebsd.org Subject: Re: 1 TB data copy Message-ID: <54db43990710120649s222eb064td2400db50a7b8e65@mail.gmail.com> In-Reply-To: <470F7545.5010808@cyberleo.net> References: <3236.67.100.188.210.1192191787.squirrel@www.geekisp.com> <20071012085956.7d8faf2d.wmoran@potentialtech.com> <470F7545.5010808@cyberleo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/12/07, CyberLeo Kitsana <cyberleo@cyberleo.net> wrote:
> Bill Moran wrote:
> > In response to "Monah Baki" <mbaki@whywire.net>:
> > I'm not completely up to speed with FreeBSD's NTFS support. Last I looked
> > at it, it was experimental and there were warnings everywhere. I assume
> > it's improved since then (~3 years ago) but can't say with authority.
>
> As I recall, the native FreeBSD NTFS support is read-only. However, the
> NTFS-3g project has a mostly complete (and pretty safe) read/write
> implementation as a FUSE program, which can be found in ports:
>
> sysutils/fusefs-ntfs
> sysutils/ntfsprogs
>
FreeBSD NTFS is not read only, but there are restrictions on what it
can write. To quote the man page:
There is limited writing ability. Limitations: file must be nonresident
and must not contain any sparses (uninitialized areas); compressed files
are also not supported. The file name must not contain multibyte charac-
ters.
If your file name uses only ASCII characters, you will be probably be
OK using mount_ntfs to write to an NTFS filesystem. I've used it for
years, but mostly for reading files. The few times I've used it for
writing, it worked fine. I think you are most likely to have problems
if you use it to edit an existing file.
- Bob
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54db43990710120649s222eb064td2400db50a7b8e65>