what's the reason why Linux can't write on NTFS partitions?
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Originally posted by Mik Linux can write on an NTFS partition. But it's risky and can cause data loss. I guess the code for writing on NTFS partitions is still not completely finished and fully tested yet.
Plus its not opensource so its all a guessing game to the developers..
There is a work around available, you can write to it, but then you have to run a scandisk and I think a few other steps to make sure the disk is not toast. It's really not worth it when you can make a fat32 filesystem, write to it, then when you boot into your NTFS OS, you can copy from the fat32 to the ntfs, and save yourself the headache.
NTFS is M$ proprietary and it is more complex than FAT(anything). It takes a lot of effort to discover how any change to a file in NTFS is recorded by NTFS, and obviously M$ will not cooperate except to provide Windoze-based APIs to those who are willing to operate within Windoze. Well, that pretty well leaves Linux out in the cold. So, Linux folks -- very smart and very patient Linux folks -- have to figure out what happens to files under NTFS and that's a very long and arduous task.
The result is that the kernel knows somethings about NTFS, but not enough to allow for rock-solid stability on updates to files within NTFS.
FAT is somewhat less complex than NTFS and is well supported in the Linux kernel. That's why most will say that if you are dual-booting with an NTFS-based Windoze, have a FAT32 partition that can be used when access to files is required with both OSes.
It all comes down to the file tables. NTFS uses a different type of file table to record and manage data. All file systems do, but because NTFS is closed sourced, it is difficult to figure out what is actually happening.
Linux read ability works well, and that is what I use. It will also copy files from NTFS, but just not write.
The best thing is to have a network file server. Sure it's just as easy to use a fat32 partition, but if you have a file server that is accessable on your network it can be used by any type of system. networking is not file system specific.