CentOS 5.5 is installed in the system. I installed the package kmod-ntfs-2.1.27-3.el5.elrepo.x86_64.rpm I mounted Seagate external hard disk. I am able to copy contents from the hard disk to the system but not from the system to the hard disk.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Ritika Garg said the following on 05/12/10 19:22:
CentOS 5.5 is installed in the system. I installed the package kmod-ntfs-2.1.27-3.el5.elrepo.x86_64.rpm I mounted Seagate external hard disk. I am able to copy contents from the hard disk to the system but not from the system to the hard disk.
Check if te file system is mounted read-only, what's the output of mount command?
Ciao, luigi
- -- / +--[Luigi Rosa]-- \
Even the smallest candle burns brighter in the dark.
On Sun, 2010-12-05 at 23:52 +0530, Ritika Garg wrote:
CentOS 5.5 is installed in the system. I installed the package kmod-ntfs-2.1.27-3.el5.elrepo.x86_64.rpm I mounted Seagate external hard disk. I am able to copy contents from the hard disk to the system but not from the system to the hard disk.
Yes. If you go to this page on the ElRepo site:
http://elrepo.org/tiki/kmod-ntfs
and check the limitations you will see that this is the expected behavior.
If you want full write capabilities with NTFS I suggest that you remove kmod-ntfs and instead use the fuse-ntfs-3g package from RPMForge. That relies on DKMS ( which works well enough for me ) and has full read-write capabilities.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Sun, 5 Dec 2010, Ron Loftin wrote:
On Sun, 2010-12-05 at 23:52 +0530, Ritika Garg wrote:
CentOS 5.5 is installed in the system. I installed the package kmod-ntfs-2.1.27-3.el5.elrepo.x86_64.rpm I mounted Seagate external hard disk. I am able to copy contents from the hard disk to the system but not from the system to the hard disk.
Yes. If you go to this page on the ElRepo site:
http://elrepo.org/tiki/kmod-ntfs
and check the limitations you will see that this is the expected behavior.
If you want full write capabilities with NTFS I suggest that you remove kmod-ntfs and instead use the fuse-ntfs-3g package from RPMForge. That relies on DKMS ( which works well enough for me ) and has full read-write capabilities.
Just a small correction. Fuse filesystems do no longer need dkms installed since the fuse kernel-module is now part of RHEL5 since RHEL 5.4. So if people still have the dkms module installed and/or use ELRepo's fuse kernel module they can safely remove it :)
On Sun, Dec 5, 2010 at 1:22 PM, Ritika Garg ritikagarg25@gmail.com wrote:
CentOS 5.5 is installed in the system. I installed the package kmod-ntfs-2.1.27-3.el5.elrepo.x86_64.rpm I mounted Seagate external hard disk. I am able to copy contents from the hard disk to the system but not from the system to the hard disk.
Do you also need the centosplus kernel, which has the NTFS features enabled in the linux kernel ".config" file at compilation time?
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Sun, 2010-12-05 at 13:40 -0500, Nico Kadel-Garcia wrote:
On Sun, Dec 5, 2010 at 1:22 PM, Ritika Garg ritikagarg25@gmail.com wrote:
CentOS 5.5 is installed in the system. I installed the package kmod-ntfs-2.1.27-3.el5.elrepo.x86_64.rpm I mounted Seagate external hard disk. I am able to copy contents from the hard disk to the system but not from the system to the hard disk.
Do you also need the centosplus kernel, which has the NTFS features enabled in the linux kernel ".config" file at compilation time?
Not for fuse-ntfs-3g. If you install the RPMForge repo, yum will do the rest, and it all plays very nicely with the CentOS standard kernels.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Sun, Dec 5, 2010 at 10:40 AM, Nico Kadel-Garcia nkadel@gmail.com wrote:
On Sun, Dec 5, 2010 at 1:22 PM, Ritika Garg ritikagarg25@gmail.com wrote:
CentOS 5.5 is installed in the system. I installed the package kmod-ntfs-2.1.27-3.el5.elrepo.x86_64.rpm I mounted Seagate external hard disk. I am able to copy contents from the hard disk to the system but not from the system to the hard disk.
Do you also need the centosplus kernel, which has the NTFS features enabled in the linux kernel ".config" file at compilation time?
Just for the record. The centosplus kernel does not have NTFS turned on. There is a bug in the NTFS code but the upstream vendor would not fix it because it is not enabled in their kernel:
https://bugzilla.redhat.com/show_bug.cgi?id=481495
Therefore it was decided not to enable it in the cplus kernel. Besides, as already pointed out in this thread, ntfs-3g is better than the kernel ntfs module functionally and it is actively maintained.
Akemi
On 12/05/10 19:22, Ritika Garg wrote:
CentOS 5.5 is installed in the system. I installed the package kmod-ntfs-2.1.27-3.el5.elrepo.x86_64.rpm I mounted Seagate external hard disk. I am able to copy contents from the hard disk to the system but not from the system to the hard disk.
The ntfs kernel module can only read. If you want write support, use ntfs-3g. It is included in rpmforge.
Ritika Garg a écrit :
CentOS 5.5 is installed in the system. I installed the package kmod-ntfs-2.1.27-3.el5.elrepo.x86_64.rpm I mounted Seagate external hard disk. I am able to copy contents from the hard disk to the system but not from the system to the hard disk.
I've been following this thread, and I'm wondering: why bother with NTFS in the first place? If you have a mixed environment where you need Windows to access your external hard disk, you might as well format it with a FAT filesystem. Linux supports FAT natively, without making you jump through burning loops.
If you don't know how to achieve this, here's how :
1) Backup all your data.
2) Given your external disk is /dev/sda, launch fdisk, delete the NTFS partition and create a single FAT partition (hex code 0b).
3) Install 'dosfstools' and format your disk :
# mkfs.vfat /dev/sda1
4) From now on, mount your disk as FAT :
# mount [-t vfat] /dev/sda1 /mnt/disk
Cheers,
Niki Kovacs
I've been following this thread, and I'm wondering: why bother with NTFS in the first place? If you have a mixed environment where you need Windows to access your external hard disk, you might as well format it with a FAT filesystem. Linux supports FAT natively, without making you jump through burning loops.
There could be many reasons why ntfs support is needed, such as reading a disk that is not your own. Also, keep in mind that FAT has a 4 GB file size limit.
On Sun, Dec 5, 2010 at 4:29 PM, Niki Kovacs contact@kikinovak.net wrote:
Ritika Garg a écrit :
CentOS 5.5 is installed in the system. I installed the package kmod-ntfs-2.1.27-3.el5.elrepo.x86_64.rpm I mounted Seagate external hard disk. I am able to copy contents from the hard disk to the system but not from the system to the hard disk.
I've been following this thread, and I'm wondering: why bother with NTFS in the first place? If you have a mixed environment where you need Windows to access your external hard disk, you might as well format it with a FAT filesystem. Linux supports FAT natively, without making you jump through burning loops.
External USB drives, USB sticks, and iSCSI devices. USB sticks, in particular, are often pre-formatted with NTFS.
At Sun, 05 Dec 2010 22:29:47 +0100 CentOS mailing list centos@centos.org wrote:
Ritika Garg a écrit :
CentOS 5.5 is installed in the system. I installed the package kmod-ntfs-2.1.27-3.el5.elrepo.x86_64.rpm I mounted Seagate external hard disk. I am able to copy contents from the hard disk to the system but not from the system to the hard disk.
I've been following this thread, and I'm wondering: why bother with NTFS in the first place? If you have a mixed environment where you need Windows to access your external hard disk, you might as well format it with a FAT filesystem. Linux supports FAT natively, without making you jump through burning loops.
If you don't know how to achieve this, here's how :
Backup all your data.
Given your external disk is /dev/sda, launch fdisk, delete the NTFS
partition and create a single FAT partition (hex code 0b).
- Install 'dosfstools' and format your disk :
# mkfs.vfat /dev/sda1
- From now on, mount your disk as FAT :
# mount [-t vfat] /dev/sda1 /mnt/disk
Cheers,
Niki Kovacs
Will FAT support the larger external disks, such as the .5TB and larger?
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Robert Heller a écrit :
Will FAT support the larger external disks, such as the .5TB and larger?
I read the replies to my previous posts, and I get your point, since I didn't know about the various limitations. It's probably due to the fact that we're 100% GNU/Linux here. I haven't booted Windows for work since before the time Windows XP came out (around 2001). The only time I get to "work" on Windows is usually to retrieve data before moving it to CentOS. As far as external hard disks are concerned, they're all ext3 here. Whenever the odd non-Linux user has to exchange data with Linux here, he or she has to use a Samba share.
So I admit my point of view is somewhat biased :o)
Cheers,
Niki
On Mon, 6 Dec 2010, Niki Kovacs wrote:
Robert Heller a écrit :
Will FAT support the larger external disks, such as the .5TB and larger?
I read the replies to my previous posts, and I get your point, since I didn't know about the various limitations. It's probably due to the fact that we're 100% GNU/Linux here. I haven't booted Windows for work since before the time Windows XP came out (around 2001). The only time I get to "work" on Windows is usually to retrieve data before moving it to CentOS. As far as external hard disks are concerned, they're all ext3 here. Whenever the odd non-Linux user has to exchange data with Linux here, he or she has to use a Samba share.
So I admit my point of view is somewhat biased :o)
However one point you make is still valid. There is no alternative to NTFS nowadays if you need so share files between Windows and Linux. It is a shame there are not better Ext3/Ext4 drivers that integrate properly into Windows.
Something similar to ntfs-3g must be easier to write for ext3 on Windows (as the ext3 format is well-known).
On Sunday, December 05, 2010 04:29:47 pm Niki Kovacs wrote:
I've been following this thread, and I'm wondering: why bother with NTFS in the first place?
It's also useful for MAC OS X and Linux data interchange. While there is a ext2 module for OS X, and there is HFS+ filesystem support for Linux, both have some issues (HFS+ on Linux; try creating a large tree of small files on HFS+, then delete said tree, and watch the kernel unmount your HFS+ filesystem in a corrupted manner; ext2 FUSE on OS X has some similar issues, but FUSE-NTFS support on both OS's is pretty solid). Usernames and permissions successful transit an NTFS filesystem, as well.
FAT is good when ownership doesn't matter, or files smaller than 4GB are used (making it less than ideal for my use, which is a shared vmware partition between VMware Workstation on linux and VMware Fusion on OS X).
On Monday, December 06, 2010 02:02:20 pm John R Pierce wrote:
On 12/06/10 8:50 AM, Lamar Owen wrote:
It's also useful for MAC OS X and Linux data interchange.
ugh. disk file systems were really not intended for data interchange, especially not NTFS. use the network.
In a dual-boot scenario?
On Monday, December 06, 2010 02:41:46 pm John R Pierce wrote:
On 12/06/10 11:12 AM, Lamar Owen wrote:
In a dual-boot scenario?
ugh. dual booting is a pain in the derriere. use a VM if its for software testing or whatever.
Some of us really do need to dual-boot, for whatever reason (mine is for audio production under OS X (until Harrison Mixbus is available in a Linux version) and everything else under Linux; OS X on VMware Workstation is to say the least unsupported.....). And, in one of my posts, I mentioned that the interchange was for VM's between Linux VMware WorkStation and OS X WMware Fusion......yeah, you really can do that, I run WinXP/2000/7 and other things under both, and with pinned MAC addresses no activation complaints....
Is it ugly? Sure; but it meets the need.
On 12/6/10 1:57 PM, Lamar Owen wrote:
On Monday, December 06, 2010 02:41:46 pm John R Pierce wrote:
On 12/06/10 11:12 AM, Lamar Owen wrote:
In a dual-boot scenario?
ugh. dual booting is a pain in the derriere. use a VM if its for software testing or whatever.
Some of us really do need to dual-boot, for whatever reason (mine is for audio production under OS X (until Harrison Mixbus is available in a Linux version) and everything else under Linux; OS X on VMware Workstation is to say the least unsupported.....).
But you could easily run Linux under Virtualbox or vmware. While still running OS X.
And, in one of my posts, I mentioned that the interchange was for VM's between Linux VMware WorkStation and OS X WMware Fusion......yeah, you really can do that, I run WinXP/2000/7 and other things under both, and with pinned MAC addresses no activation complaints....
I thought VMware (maybe virtualbox too) had a built-in way to share files from the host. In any case you can do network samba/nfs shares that the VM's can see just like you would if they were physical machines or on a different host.
On Monday, December 06, 2010 03:50:49 pm Les Mikesell wrote:
But you could easily run Linux under Virtualbox or vmware. While still running OS X.
I'd rather not do that, as performance does suffer to a degree, and Linux is my primary environment, not my secondary one. Further, you then add a layer of complexity with VMware tools and kernel updates and recompiling (assuming the VMware tools will even recompile on the latest Fedora kernel..).... no thank you. I much prefer to keep my primary environment as Linux and boot into OS X when I need to do audio production. I rarely do 'normal' things when I'm doing audio production anyway, so it works for me quite well, and I get full native performance under Linux for the things I do there (which includes GNUradio with a USRP, which doesn't work well in a VM, partly because VMware and accurate timekeeping are at odds with each other).
I thought VMware (maybe virtualbox too) had a built-in way to share files from the host. In any case you can do network samba/nfs shares that the VM's can see just like you would if they were physical machines or on a different host.
Yes; that's HGFS, and it works ok, but has its quirks.
That doesn't help in terms of the storage where the vmdk disk images are located.
At Mon, 06 Dec 2010 11:02:20 -0800 CentOS mailing list centos@centos.org wrote:
On 12/06/10 8:50 AM, Lamar Owen wrote:
It's also useful for MAC OS X and Linux data interchange.
ugh. disk file systems were really not intended for data interchange, especially not NTFS. use the network.
That assumes that you have enough network bandwidth... Some of us just don't have enough bandwidth. "Never underestimate the bandwidth of a station wagon full of tapes", or that little USB connected "drive" in your pocket...
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Akemi Yagi -
Barry Brimer -
Dag Wieers -
John R Pierce -
Lamar Owen -
Les Mikesell -
Luigi Rosa -
Nico Kadel-Garcia -
Niki Kovacs -
RedShift -
Ritika Garg -
Robert Heller -
Ron Loftin