• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

ntfs-3g FUSE kernel module (Linux)

X

xtknight

Elite Member
I tried compiling it for my 64-bit Ubuntu Dapper system. It did compile and I inserted it into the kernel. I was able to mount my NTFS partition and read/write. However, the files I wrote were totally corrupt when I tried to open them up in Windows (Windows showed an error message saying the folder was unreadable). I wasn't able to read them in Linux either after I rebooted. Read support for Windows-created files seems to work just fine (like it always has).

What's really odd is I think it works for some people. One of the tutorials said 64-bit wasn't supported but that doesn't make any sense. They provided sources and I should be able to compile for my 64-bit system. He must have been talking about somebody's pre-made 32-bit Debian packages.
 
I tried it. It sorta works. I can make files and directories, but Windows detects some of them as corrupt and removes them sometimes.
 
Originally posted by: SleepWalkerX
I tried it. It sorta works. I can make files and directories, but Windows detects some of them as corrupt and removes them sometimes.
Click to expand...

If I recall you run SUSE 10.1 64-bit right? Have you had a chance to try it on a 32-bit distro?
 
What's really odd is I think it works for some people. One of the tutorials said 64-bit wasn't supported but that doesn't make any sense. They provided sources and I should be able to compile for my 64-bit system.
Click to expand...

Why is that strange? There is a lot of code that isn't 64bit safe.
 
Originally posted by: xtknight
The ./configure and compile would still pass even if it didn't run with 64-bit?
Click to expand...
Sure, how's the compiler going to know that the code isn't playing by the rules? And filesystems are probably one of the most sensitive areas in this regard, given that you're dealing with a lot of data that doesn't fit cleanly into normal c types.
 
It just seems like they'd exclude it in the configure. Anyway does anyone know the official page for ntfs-3g?

Edit: Here: http://www.linux-ntfs.org/ but there's little info on it.

On 64-bit: Problem: Why doesn't the driver work on 64-bit and big-endian systems?
Answer: The code is 64-bit ready and almost fully endian safe, however
we are unable to validate the functionality and keep ensuring
correctness for the future due to lack of target hardwares.
 
Originally posted by: xtknight
It just seems like they'd exclude it in the configure. Anyway does anyone know the official page for ntfs-3g?

Edit: Here: http://www.linux-ntfs.org/ but there's little info on it.

On 64-bit: Problem: Why doesn't the driver work on 64-bit and big-endian systems?
Answer: The code is 64-bit ready and almost fully endian safe, however
we are unable to validate the functionality and keep ensuring
correctness for the future due to lack of target hardwares.
Click to expand...

Send them hardware. 🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top