Linked by Eugenia Loli on Sun 7th Jan 2007 19:24 UTC, submitted by falko
Thread beginning with comment 199393
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
More News »
Sponsored Links



Member since:
2006-08-25
i've used ntfs-3g pretty much since its first public release on Kanotix (and now Sidux), and i've never experienced any serious problems with it. and i used it HEAVILY since my main data storage partition is in NTFS. it never "refused to perform the action" through all the large archive extractions and torrent downloads that i put it through. and not a single file corruption.
i only encountered a problem when i accidentally created a folder with a name ending with ".", which Windows doesn't like. going back to linux and renaming the folder solved the problem. also, during heavy read/write operations (such as with torrents), CPU usage can get pretty high sometimes.
AFAIK the only real limitation of ntfs-3g is that it doesn't support compressed and/or encrypted ntfs wolumes.