I have here a box which I dual-boot between CentOS 5.4 and an older version of that "other OS" that I'm using to check out the ELrepo version of kmod-ntfs. After installing as per the directions on the ELrepo site, I can mount an NTFS filesystem, and when I type "mount" with no options the output tells me that the target filesystem is mounted read-write. However, when I try to create a file on that filesystem as root, I get a "Permission denied" error, which leads me to think that I'm missing something here. So far, Google has not been very helpful here, so if anyone can shine some light on this, it would be welcome.
On Saturday 31 October 2009 20:12, Ron Loftin wrote:
I have here a box which I dual-boot between CentOS 5.4 and an older version of that "other OS" that I'm using to check out the ELrepo version of kmod-ntfs. After installing as per the directions on the ELrepo site, I can mount an NTFS filesystem, and when I type "mount" with no options the output tells me that the target filesystem is mounted read-write. However, when I try to create a file on that filesystem as root, I get a "Permission denied" error, which leads me to think that I'm missing something here. So far, Google has not been very helpful here, so if anyone can shine some light on this, it would be welcome.
Try using "mount -t ntfs-3g" rather than "mount -t ntfs". You may have to install fuse-ntfs-3g.
On Sat, 2009-10-31 at 23:39 -0400, Yves Bellefeuille wrote:
On Saturday 31 October 2009 20:12, Ron Loftin wrote:
I have here a box which I dual-boot between CentOS 5.4 and an older version of that "other OS" that I'm using to check out the ELrepo version of kmod-ntfs. After installing as per the directions on the ELrepo site, I can mount an NTFS filesystem, and when I type "mount" with no options the output tells me that the target filesystem is mounted read-write. However, when I try to create a file on that filesystem as root, I get a "Permission denied" error, which leads me to think that I'm missing something here. So far, Google has not been very helpful here, so if anyone can shine some light on this, it would be welcome.
Try using "mount -t ntfs-3g" rather than "mount -t ntfs". You may have to install fuse-ntfs-3g.
I think that you have misunderstood my question. I know how to do it with the packages from RPMforge ( which is where I get fuse-ntfs-3g ) but I'm trying to evaluate the kmod-ntfs package from ELrepo.org. There seems to be something I'm not understanding about this approach, or I'm not finding the correct documentation for it.
On Sat, Oct 31, 2009 at 11:14 PM, Ron Loftin reloftin@twcny.rr.com wrote:
On Sat, 2009-10-31 at 23:39 -0400, Yves Bellefeuille wrote:
On Saturday 31 October 2009 20:12, Ron Loftin wrote:
I have here a box which I dual-boot between CentOS 5.4 and an older version of that "other OS" that I'm using to check out the ELrepo version of kmod-ntfs. After installing as per the directions on the ELrepo site, I can mount an NTFS filesystem, and when I type "mount" with no options the output tells me that the target filesystem is mounted read-write. However, when I try to create a file on that filesystem as root, I get a "Permission denied" error, which leads me to think that I'm missing something here. So far, Google has not been very helpful here, so if anyone can shine some light on this, it would be welcome.
Try using "mount -t ntfs-3g" rather than "mount -t ntfs". You may have to install fuse-ntfs-3g.
I think that you have misunderstood my question. I know how to do it with the packages from RPMforge ( which is where I get fuse-ntfs-3g ) but I'm trying to evaluate the kmod-ntfs package from ELrepo.org. There seems to be something I'm not understanding about this approach, or I'm not finding the correct documentation for it.
This statement is a direct quote from CentOS Wiki (
http://wiki.centos.org/TipsAndTricks/NTFS)
[image: <!>] As of CentOS 5.4 (kernel 2.6.18-164 or newer), the fuse kernel module is included in the kernel itself. Therefore, dkms and dkms-fuse are no longer required. If you have previously installed dkms-fuse, please * uninstall* it by a *yum remove dkms-fuse* command.
On Sat, Oct 31, 2009 at 8:14 PM, Ron Loftin reloftin@twcny.rr.com wrote:
I have here a box which I dual-boot between CentOS 5.4 and an older version of that "other OS" that I'm using to check out the ELrepo version of kmod-ntfs. After installing as per the directions on the ELrepo site, I can mount an NTFS filesystem, and when I type "mount" with no options the output tells me that the target filesystem is mounted read-write. However, when I try to create a file on that filesystem as root, I get a "Permission denied" error, which leads me to think that I'm missing something here. So far, Google has not been very helpful here, so if anyone can shine some light on this, it would be welcome.
but I'm trying to evaluate the kmod-ntfs package from ELrepo.org. There seems to be something I'm not understanding about this approach, or I'm not finding the correct documentation for it.
Could you show us the output returned by:
uname -mr ls -l `find /lib/modules -name ntfs.ko` ls -l `find /lib/modules -name fuse.ko`
Akemi
On Sun, 2009-11-01 at 14:49 -0800, Akemi Yagi wrote:
On Sat, Oct 31, 2009 at 8:14 PM, Ron Loftin reloftin@twcny.rr.com wrote:
I have here a box which I dual-boot between CentOS 5.4 and an older version of that "other OS" that I'm using to check out the ELrepo version of kmod-ntfs. After installing as per the directions on the ELrepo site, I can mount an NTFS filesystem, and when I type "mount" with no options the output tells me that the target filesystem is mounted read-write. However, when I try to create a file on that filesystem as root, I get a "Permission denied" error, which leads me to think that I'm missing something here. So far, Google has not been very helpful here, so if anyone can shine some light on this, it would be welcome.
but I'm trying to evaluate the kmod-ntfs package from ELrepo.org. There seems to be something I'm not understanding about this approach, or I'm not finding the correct documentation for it.
Could you show us the output returned by:
uname -mr ls -l `find /lib/modules -name ntfs.ko` ls -l `find /lib/modules -name fuse.ko`
uname -mr 2.6.18-164.2.1.el5 i686
ls -l `find /lib/modules -name ntfs.ko` lrwxrwxrwx 1 root root 46 Oct 31 19:45 /lib/modules/2.6.18-164.2.1.el5/weak-updates/ntfs/ntfs.ko -> /lib/modules/2.6.18-128.el5/extra/ntfs/ntfs.ko lrwxrwxrwx 1 root root 46 Oct 31 19:45 /lib/modules/2.6.18-92.1.13.el5/weak-updates/ntfs/ntfs.ko -> /lib/modules/2.6.18-128.el5/extra/ntfs/ntfs.ko
ls -l `find /lib/modules -name fuse.ko` -rwxr--r-- 1 root root 57464 Sep 30 15:26 /lib/modules/2.6.18-164.2.1.el5/kernel/fs/fuse/fuse.ko
Be careful of the line wrapping, and thanks for the help.
Akemi _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Sun, Nov 1, 2009 at 3:09 PM, Ron Loftin reloftin@twcny.rr.com wrote:
On Sun, 2009-11-01 at 14:49 -0800, Akemi Yagi wrote:
Could you show us the output returned by:
uname -mr ls -l `find /lib/modules -name ntfs.ko` ls -l `find /lib/modules -name fuse.ko`
uname -mr 2.6.18-164.2.1.el5 i686
ls -l `find /lib/modules -name ntfs.ko` lrwxrwxrwx 1 root root 46 Oct 31 19:45 /lib/modules/2.6.18-164.2.1.el5/weak-updates/ntfs/ntfs.ko -> /lib/modules/2.6.18-128.el5/extra/ntfs/ntfs.ko lrwxrwxrwx 1 root root 46 Oct 31 19:45 /lib/modules/2.6.18-92.1.13.el5/weak-updates/ntfs/ntfs.ko -> /lib/modules/2.6.18-128.el5/extra/ntfs/ntfs.ko
Something is wrong here. You are missing /lib/modules/2.6.18-128.el5/extra/ntfs/ntfs.ko that the symlinks are pointing to. Are those symlinks red-blinking?
ls -l `find /lib/modules -name fuse.ko` -rwxr--r-- 1 root root 57464 Sep 30 15:26 /lib/modules/2.6.18-164.2.1.el5/kernel/fs/fuse/fuse.ko
This one is as expected. Just fine.
Akemi
On Sun, 2009-11-01 at 15:20 -0800, Akemi Yagi wrote:
On Sun, Nov 1, 2009 at 3:09 PM, Ron Loftin reloftin@twcny.rr.com wrote:
On Sun, 2009-11-01 at 14:49 -0800, Akemi Yagi wrote:
Could you show us the output returned by:
uname -mr ls -l `find /lib/modules -name ntfs.ko` ls -l `find /lib/modules -name fuse.ko`
uname -mr 2.6.18-164.2.1.el5 i686
ls -l `find /lib/modules -name ntfs.ko` lrwxrwxrwx 1 root root 46 Oct 31 19:45 /lib/modules/2.6.18-164.2.1.el5/weak-updates/ntfs/ntfs.ko -> /lib/modules/2.6.18-128.el5/extra/ntfs/ntfs.ko lrwxrwxrwx 1 root root 46 Oct 31 19:45 /lib/modules/2.6.18-92.1.13.el5/weak-updates/ntfs/ntfs.ko -> /lib/modules/2.6.18-128.el5/extra/ntfs/ntfs.ko
Something is wrong here. You are missing /lib/modules/2.6.18-128.el5/extra/ntfs/ntfs.ko that the symlinks are pointing to. Are those symlinks red-blinking?
It's there. I must have missed it with my cut-and-paste before.
( Side note: I can't stand all that color-coding with the "ls" command, so I disable it. That's just my prejudice from growing up with UNIX in the '80s and '90s on REAL monochrome terminals. ;)
ls -l /lib/modules/2.6.18-128.el5/extra/ntfs/ntfs.ko -rw-r--r-- 1 root root 235684 Oct 9 13:00 /lib/modules/2.6.18-128.el5/extra/ntfs/ntfs.ko
ls -l `find /lib/modules -name fuse.ko` -rwxr--r-- 1 root root 57464 Sep 30 15:26 /lib/modules/2.6.18-164.2.1.el5/kernel/fs/fuse/fuse.ko
This one is as expected. Just fine.
Akemi _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Sun, Nov 1, 2009 at 3:42 PM, Ron Loftin reloftin@twcny.rr.com wrote:
On Sun, 2009-11-01 at 15:20 -0800, Akemi Yagi wrote:
Something is wrong here. You are missing /lib/modules/2.6.18-128.el5/extra/ntfs/ntfs.ko that the symlinks are pointing to. Are those symlinks red-blinking?
It's there. I must have missed it with my cut-and-paste before.
( Side note: I can't stand all that color-coding with the "ls" command, so I disable it. That's just my prejudice from growing up with UNIX in the '80s and '90s on REAL monochrome terminals. ;)
I fully understand (similar generation?!).
ls -l /lib/modules/2.6.18-128.el5/extra/ntfs/ntfs.ko -rw-r--r-- 1 root root 235684 Oct 9 13:00 /lib/modules/2.6.18-128.el5/extra/ntfs/ntfs.ko
Alright. Then as far as installation of the modules are concerned, there does not seem to be a problem. So, just for a confirmation, 'modprobe ntfs' and 'modprobe fuse' run without any errors and lsmod shows both modules loaded?
If ntfs-3g is working for you, I would expect the ntfs module from kmod-ntfs works, too. However, they are not the same. The latter was built from the ntfs code in CentOS 5.3 (which was originally broken). I believe it worked after a patch was applied and this was tested by CentOS QA members.
Akemi
On Sun, 2009-11-01 at 16:41 -0800, Akemi Yagi wrote:
On Sun, Nov 1, 2009 at 3:42 PM, Ron Loftin reloftin@twcny.rr.com wrote:
On Sun, 2009-11-01 at 15:20 -0800, Akemi Yagi wrote:
Something is wrong here. You are missing /lib/modules/2.6.18-128.el5/extra/ntfs/ntfs.ko that the symlinks are pointing to. Are those symlinks red-blinking?
It's there. I must have missed it with my cut-and-paste before.
( Side note: I can't stand all that color-coding with the "ls" command, so I disable it. That's just my prejudice from growing up with UNIX in the '80s and '90s on REAL monochrome terminals. ;)
I fully understand (similar generation?!).
ls -l /lib/modules/2.6.18-128.el5/extra/ntfs/ntfs.ko -rw-r--r-- 1 root root 235684 Oct 9 13:00 /lib/modules/2.6.18-128.el5/extra/ntfs/ntfs.ko
Alright. Then as far as installation of the modules are concerned, there does not seem to be a problem. So, just for a confirmation, 'modprobe ntfs' and 'modprobe fuse' run without any errors and lsmod shows both modules loaded?
Seems to work. Both "modprobe" commands run with no error, and lsmod shows this:
lsmod | egrep 'fuse|ntfs' fuse 49237 0 ntfs 196760 0
If ntfs-3g is working for you, I would expect the ntfs module from kmod-ntfs works, too.
That's what I thought. However, when I mount a partition created with Windoze 2000, I can read files and directories, but not create or modify anything. Here's the actual scenario ( all commands performed as root):
# dmesg | tail FS-Cache: Loaded [drm] Initialized drm 1.0.1 20051102 ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 9 PCI: setting IRQ 9 as level-triggered ACPI: PCI Interrupt 0000:00:01.0[A] -> Link [LNKA] -> GSI 9 (level, low) -> IRQ 9 [drm] Initialized i810 1.4.0 20030605 on minor 0 [drm] Using v1.4 init. NTFS driver 2.1.27 [Flags: R/W MODULE]. fuse init (API version 7.10) NTFS volume version 3.0.
# fdisk -l /dev/hda
Disk /dev/hda: 8700 MB, 8700346368 bytes 255 heads, 63 sectors/track, 1057 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System /dev/hda1 * 1 522 4192933+ 7 HPFS/NTFS /dev/hda2 523 1056 4289355 f W95 Ext'd (LBA) /dev/hda5 523 783 2096451 7 HPFS/NTFS /dev/hda6 784 1056 2192841 b W95 FAT32
# mount /dev/hda5 /mnt ( no error returned )
# mount /dev/hdb1 on / type ext3 (rw,nodev) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/hdb3 on /var type ext3 (rw,nosuid,nodev) /dev/hdb2 on /tmp type ext3 (rw,nosuid,nodev) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) /dev/hda5 on /mnt type ntfs (rw)
Note the last line claims that hda5 is mounted with type "ntfs" and "rw".
# /bin/ls -la /mnt total 1048592 drwx------ 1 root root 4096 Oct 31 22:47 . drwxr-xr-x 26 root root 4096 Nov 1 19:05 .. -rw------- 1 root root 1073741824 Oct 31 22:43 pagefile.sys drwx------ 1 root root 0 Feb 2 2006 RECYCLER drwx------ 1 root root 0 Oct 31 21:31 spool drwx------ 1 root root 0 Jan 24 2006 System Volume Information drwx------ 1 root root 4096 Oct 31 22:50 tmp
# touch /mnt/testfile touch: cannot touch `/mnt/testfile': Permission denied # touch /mnt/tmp/testfile touch: cannot touch `/mnt/tmp/testfile': Permission denied
So, what am I missing, and where should I look ?
However, they are not the same. The latter was built from the ntfs code in CentOS 5.3 (which was originally broken). I believe it worked after a patch was applied and this was tested by CentOS QA members.
Akemi _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Sun, Nov 1, 2009 at 5:05 PM, Ron Loftin reloftin@twcny.rr.com wrote:
If ntfs-3g is working for you, I would expect the ntfs module from kmod-ntfs works, too.
That's what I thought. However, when I mount a partition created with Windoze 2000, I can read files and directories, but not create or modify anything. Here's the actual scenario ( all commands performed as root):
(big snip)
So, what am I missing, and where should I look ?
Looks like you are doing everything just fine. Perhaps, we should move this conversation to the ELRepo mailing list because this is now all about kmod-ntfs and not all members of the ELRepo team are reading this mailing list on a regular basis.
http://elrepo.org/tiki/MailingLists
What do you think?
Akemi
On Sun, 2009-11-01 at 17:38 -0800, Akemi Yagi wrote:
On Sun, Nov 1, 2009 at 5:05 PM, Ron Loftin reloftin@twcny.rr.com wrote:
If ntfs-3g is working for you, I would expect the ntfs module from kmod-ntfs works, too.
That's what I thought. However, when I mount a partition created with Windoze 2000, I can read files and directories, but not create or modify anything. Here's the actual scenario ( all commands performed as root):
(big snip)
So, what am I missing, and where should I look ?
Looks like you are doing everything just fine. Perhaps, we should move this conversation to the ELRepo mailing list because this is now all about kmod-ntfs and not all members of the ELRepo team are reading this mailing list on a regular basis.
http://elrepo.org/tiki/MailingLists
What do you think?
I think that I just signed up for the ELRepo mailing list. I will post my last message there ( unless you think more of the background is useful ) and see what turns up.
Akemi _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Sun, Nov 1, 2009 at 5:46 PM, Ron Loftin reloftin@twcny.rr.com wrote:
On Sun, 2009-11-01 at 17:38 -0800, Akemi Yagi wrote:
Looks like you are doing everything just fine. Perhaps, we should move this conversation to the ELRepo mailing list because this is now all about kmod-ntfs and not all members of the ELRepo team are reading this mailing list on a regular basis.
http://elrepo.org/tiki/MailingLists
What do you think?
I think that I just signed up for the ELRepo mailing list. I will post my last message there ( unless you think more of the background is useful ) and see what turns up.
Adding the link to your original post of this thread will help:
http://lists.centos.org/pipermail/centos/2009-November/084896.html
Akemi
On Sun, Nov 1, 2009 at 5:49 PM, Akemi Yagi amyagi@gmail.com wrote:
On Sun, Nov 1, 2009 at 5:46 PM, Ron Loftin reloftin@twcny.rr.com wrote:
On Sun, 2009-11-01 at 17:38 -0800, Akemi Yagi wrote:
Looks like you are doing everything just fine. Perhaps, we should move this conversation to the ELRepo mailing list because this is now all about kmod-ntfs and not all members of the ELRepo team are reading this mailing list on a regular basis.
http://elrepo.org/tiki/MailingLists
What do you think?
I think that I just signed up for the ELRepo mailing list. I will post my last message there ( unless you think more of the background is useful ) and see what turns up.
Adding the link to your original post of this thread will help:
http://lists.centos.org/pipermail/centos/2009-November/084896.html
This is just a followup post for those who would like to know how this conversation developed. The details are in this ELRepo mailing list thread:
http://lists.elrepo.org/pipermail/elrepo/2009-November/000102.html
In short, the write support offered by the kernel (hence kmod-ntfs) is quite limited. Alan Bartlett pointed to this section of the kernel Kconfig file:
"The only supported operation is overwriting existing files, without changing the file length. No file or directory creation, deletion or renaming is possible. Note only non-resident files can be written to so you may find that some very small files (<500 bytes or so) cannot be written to."
Conclusion is, if you need to write to NTFS, you should use ntfs-3g.
Akemi
This is just a followup post for those who would like to know how this conversation developed. The details are in this ELRepo mailing list thread:
http://lists.elrepo.org/pipermail/elrepo/2009-November/000102.html
In short, the write support offered by the kernel (hence kmod-ntfs) is quite limited. Alan Bartlett pointed to this section of the kernel Kconfig file:
"The only supported operation is overwriting existing files, without changing the file length. No file or directory creation, deletion or renaming is possible. Note only non-resident files can be written to so you may find that some very small files (<500 bytes or so) cannot be written to."
Conclusion is, if you need to write to NTFS, you should use ntfs-3g.
Akemi
I can write, rename, create folders and files under kernel -2.6.18-164.2.1.el5
On Tue, Nov 3, 2009 at 6:43 AM, Rod Rook rod.rook@gmail.com wrote:
In short, the write support offered by the kernel (hence kmod-ntfs) is quite limited. Alan Bartlett pointed to this section of the kernel Kconfig file:
"The only supported operation is overwriting existing files, without changing the file length. No file or directory creation, deletion or renaming is possible. Note only non-resident files can be written to so you may find that some very small files (<500 bytes or so) cannot be written to."
Conclusion is, if you need to write to NTFS, you should use ntfs-3g.
I can write, rename, create folders and files under kernel -2.6.18-164.2.1.el5
Using the in-kernel ntfs module (kmod-ntfs) ?
Akemi
On Tue, Nov 3, 2009 at 8:55 AM, Akemi Yagi amyagi@gmail.com wrote:
On Tue, Nov 3, 2009 at 6:43 AM, Rod Rook rod.rook@gmail.com wrote:
In short, the write support offered by the kernel (hence kmod-ntfs) is quite limited. Alan Bartlett pointed to this section of the kernel Kconfig file:
"The only supported operation is overwriting existing files, without changing the file length. No file or directory creation, deletion or renaming is possible. Note only non-resident files can be written to so you may find that some very small files (<500 bytes or so) cannot be written to."
Conclusion is, if you need to write to NTFS, you should use ntfs-3g.
I can write, rename, create folders and files under kernel -2.6.18-164.2.1.el5
Using the in-kernel ntfs module (kmod-ntfs) ?
Akemi
Yes.
On Tue, Nov 3, 2009 at 6:58 AM, Rod Rook rod.rook@gmail.com wrote:
On Tue, Nov 3, 2009 at 8:55 AM, Akemi Yagi amyagi@gmail.com wrote:
I can write, rename, create folders and files under kernel -2.6.18-164.2.1.el5
Using the in-kernel ntfs module (kmod-ntfs) ?
Yes.
Interesting (and curious). That means that the description in the Kconfig file is obsolete. Thanks for your input.
My attempt to write to NTFS produced a "permission denied" message. This needs more investigation.
Akemi
Interesting (and curious). That means that the description in the Kconfig file is obsolete. Thanks for your input.
My attempt to write to NTFS produced a "permission denied" message. This needs more investigation.
Akemi
You could have saved lots of time and efforts if you cared to read the directions as given in CentOS Wiki ( ( http://wiki.centos.org/TipsAndTricks/NTFS) ) as I had suggested in this thread.
Rod Rook wrote:
Interesting (and curious). That means that the description in the Kconfig file is obsolete. Thanks for your input. My attempt to write to NTFS produced a "permission denied" message. This needs more investigation. AkemiYou could have saved lots of time and efforts if you cared to read the directions as given in CentOS Wiki ( (http://wiki.centos.org/TipsAndTricks/NTFS) ) as I had suggested in this thread.
funny. Rod, that wiki page ends with: "Written and currently maintained by AkemiYagi. Comments/improvement welcome." I guess the Akemi you replied to had read that page :-D . and I suspect you are actually using ntfs-3g...
On Tue, Nov 3, 2009 at 7:44 AM, Nicolas Thierry-Mieg Nicolas.Thierry-Mieg@imag.fr wrote:
funny. Rod, that wiki page ends with: "Written and currently maintained by AkemiYagi. Comments/improvement welcome." I guess the Akemi you replied to had read that page :-D . and I suspect you are actually using ntfs-3g...
Not only I have read it but I actually created that wiki article... :-D
Akemi
On Tue, Nov 3, 2009 at 8:00 AM, Akemi Yagi amyagi@gmail.com wrote:
On Tue, Nov 3, 2009 at 7:44 AM, Nicolas Thierry-Mieg Nicolas.Thierry-Mieg@imag.fr wrote:
and I suspect you are actually using ntfs-3g...
Indeed, this has to be looked into.
Rod, could you show us the output from:
rpm -qa kmod*
and
ls -l `find /lib/modules -name ntfs.ko` (if this command gives you a list of your current directory, then please don't post the output)
Thanks,
Akemi
On Tue, 3 Nov 2009, Akemi Yagi wrote:
On Tue, Nov 3, 2009 at 8:00 AM, Akemi Yagi amyagi@gmail.com wrote:
On Tue, Nov 3, 2009 at 7:44 AM, Nicolas Thierry-Mieg Nicolas.Thierry-Mieg@imag.fr wrote:
and I suspect you are actually using ntfs-3g...
Indeed, this has to be looked into.
Rod, could you show us the output from:
rpm -qa kmod*
and
ls -l `find /lib/modules -name ntfs.ko` (if this command gives you a list of your current directory, then please don't post the output)
Beware that even when the ntfs kernel module is loaded, it doesn't mean that you are not using ntfs-3g. Especially if you are using automounting it might still pick ntfs-3g as mount.ntfs ships with ntfs-3g (or when using gnome even gnome-vfs2-ntfs) over kmod-ntfs.
On Wed, Nov 4, 2009 at 10:18 AM, Dag Wieers dag@wieers.com wrote:
On Tue, 3 Nov 2009, Akemi Yagi wrote:
rpm -qa kmod*
and
ls -l `find /lib/modules -name ntfs.ko` (if this command gives you a list of your current directory, then please don't post the output)
Beware that even when the ntfs kernel module is loaded, it doesn't mean that you are not using ntfs-3g. Especially if you are using automounting it might still pick ntfs-3g as mount.ntfs ships with ntfs-3g (or when using gnome even gnome-vfs2-ntfs) over kmod-ntfs.
Ah, thanks for pointing that out.
locate ntfs.ko
and
modprobe ntfs ; modinfo ntfs
might provide more useful info.
Akemi
On Sat, 31 Oct 2009, Ron Loftin wrote:
ELrepo site, I can mount an NTFS filesystem, and when I type "mount" with no options the output tells me that the target filesystem is mounted read-write. However, when I try to create a file on that filesystem as root, I get a "Permission denied" error, which leads me to think that I'm missing something here.
Stupid question: BEFORE you mount, what are the permissions on the mount point? Those permissions can affect what you can do with the mounted filesystem.
Once you mount the filesystem it's awfully hard to figure out what the problem is because the original mount point permissions are hidden...
That one has gotten me before, but a wiser SA than myself warned me before I ever came across it, so I didn't spin my wheels _too_ long looking for the problem! That would have been a real hair-puller otherwise.
I don't know whether current Unix/Linux systems behave in the same manner, but SunOS/Solaris used to.
-
Akemi Yagi -
Curt Mills -
Dag Wieers -
Nicolas Thierry-Mieg -
Rod Rook -
Ron Loftin -
Yves Bellefeuille