I am running on Fedora Core 6 and I want to have write access to my Windows partition. I have already done the following steps :

a) yum -y install ntfs-3g (after in SU mode)
b) md /mnt/windows
c) Added the following line
/dev/hda1 /mnt/windows ntfs-3g rw,defaults,umask=0000 0 0

But the problem is when the system is booting up it is saying write permission error /dev/fuse.

Can anyone suggest me where I am going wrong?

Hi arindom
Run in a console as root :
ntfs-3g /dev/hda1 /mnt/windows

and tell the exact error messages you get.

Hello berbae,

Thanks for your suggestions. I have done as what you suggested and I got the following message.
-------------------------------------
Error opening partition device: Device or resource busy
Failed to startup volume: Device or resource busy
Failed to mount '/dev/hda1': Device or resource busy
Mount is denied because the NTFS volume is already exclusively opened.
The volume may be already mounted, or another software may use it which
could be identified for example by the help of the 'fuser' command.
--------------------------------------

I think this is because I have already opened my /dev/hda1 as pre /etc/fstab entry, which is :
/dev/hda1 /mnt/windows ntfs ro,defaults,umask=0222 0 0

As I have mentioned earlier that I had tried loading ntfs-3g but the problem is when I am writing in the /etc/fstab as :
/dev/hda1 /mnt/windows ntfs-3g rw,defaults,umask=0000 0 0

I am getting an error while booting "write permission error /dev/fuse".

This is the problem. If you need any further information to help me solve this problem I will be posting that here.

This is what i have in my fstab (and it works!):

/dev/hda1 /home/kaname/Win/Sys ntfs-3g locale=hu_HU.utf8 0 0

I hope it helps.

Thanks Kaname, I will check that and let you know.

No same problem. It's not working.

You wrote :
This is that error that I want exact details on.
So can you run in a console as root:
and tell exactly all the error message.
also can you tell the results of these commands:
rpm -q ntfs-3g fuse
uname -r
lsmod|grep fuse
dmesg|grep fuse

removed by linux-goot (sorry, bad information for topic!).

Unless you are trying to trash your ntfs partition you're better off to not write to it from your Linux partition. ntfs write support is still not perfected and you run a very real risk of creating some real problems for yourself.

That's an advise I would follow. No point in trying to trash my NTFS. Still I must thanks berbae for the help.

masonm wrote:
Where have you seen that concerning the ntfs-3g project?
Though still in beta stage, it has reached very good liability.
Go to ntfs-3g.org for fresh news about the project.
Many already use the driver and have found a real advancement in the resolution of the writing issue to ntfs partitions.
Also the driver is about to be integrated in several linux distros.
So I think the mansonm statement is obsolete presently or at least largely exaggerated about the risk.

As stated, that project is still in beta. While I have read some good things about it, I would not want to trust critical file systems to a beta (testing) project. But it's your system so do what you want.

If the project ever makes it to the stable package stage it may well a good thing. If it does it will eventually be incorporated into the ntfsprogs package. But, that said, beta is beta and any time one uses a package that is under development and testing they run a risk of problems. The standard disclaimer for any beta package is "use at your own risk".

It's not a reason to use a very negative approach and to discourage other to use it by a FUD post.
"If the project ever makes it to the stable package stage" it will not be by your
contribution with such a view.
The actual beta stage is not caused by data corruption risks but only by "certain usability issues and driver limitations" which is far from "a very real risk of creating some real problems for yourself."
Good wishes to you nevertheless.

FUD? You're kidding right? I was telling him the simple truth. It IS still in beta and it's only fair to tell a newbie that fact and what it means. There is in fact a risk any time one chooses to use a beta stage package and it's highly unfair to a newbie to not make certain that they are aware of that fact.

And while I don't know what contributions you have made to Linux over the years, I do know that I have made a good many of them, including helping to debug alpha and beta stage apps many times. But I have never tried to represent any beta package as 100% stable which is highly dishonest.

Arindom quite probably hit a SELinux bug which is explained here with the solution: http://www.ntfs-3g.org/support.html#selinux

Ntfs-3g is quite widely used already and there isn't anything wrong with its reliability. In fact, most distributions already replaced the "stable" captive-ntfs with the "beta" ntfs-3g because it's miles ahead both in reliability and speed.