Fedora :: Writing To NTFS Causes Fragmentation / Solve This?
Aug 26, 2010
For some reason when i write a file to my NTFS-partitioned external HDD the files seem to get severely partitioned. This only happens when writing to it from within Fedora.
Windows Vista doesn't seem to do this.
This image is a screenshot from MyDefrag.
On my other hard drive i have a 7GB file consisting of 1400 fragments.
i'm guessing this is too much fragmented, because it was a completely empty hard drive before it wrote the file.
What could have caused this please? and how can i solve this?
I'm new to OpenSuse 11.2, In Yast partitions configurations, I've mounted all NTFS partitions successfully without ticking "read-only", and according to this webpage: NTFS - openSUSE I checked my fstab file, there's no "-ro" in the file. But I still couldn't write to any mounted NTFS partitions, I can't do paste file, can't save changed files into NTFS partition.
My main workstation incorporates a mixture of ext3, ext4, and NTFS partitions scattered across a number of hard drives. Several of the ext4 partitions are encrypted, and I intend to encrypt the rest of the Linux partitions in the near future.I run VMware workstation, with several Windows OS guests, including Win2K, WinXP and Win7. My Win7 VM is installed on a virtual hard disk, and that virtual hard disk is encrypted using VMware facilities.So this leaves me with a bunch of NTFS partitions that are not encrypted. These are physical partitions on a couple of different hard drives. The reason I have them is ancient and historical, and as I have upgraded my system over time I have maintained the architecture due to the extreme difficulty of rearranging Windows systems.I still need to maintain Win2K and WinXP support, and rearranging those virtual machines would represent a hideous nightmare for me; I really want to maintain the same hard drive partition architecture.But I want to encrypt the NTFS partitions, in a fashion that can be handled by any of the Windows operating systems, AND can be accessed for read and write from Linux.Is this possible? If not using Windows facilities (I don't think ntfs-3g handles encryption, and there are known backdoors in the Windows facilities anyway), is there any third party solution that would work? Would True Crypt do the job in a fashion that would permit access from all the various operating systems, as required? I do generally mount the NTFS partitions in whichever Windows VM is appropriate, then share them out via SMB, but there are circumstances (like when a VM is not running) where I will directly hit them from Linux. So, it is possible for me to contemplate a solution that only works from Windows, but this would cost me the ability to repair/modify those filesystems directly from Linux, which under certain circumstances (a malfunction of the VM, for instance) could be a problem.
I'm fairly new to linux and I have a dual boot laptop with OpenSUSE 11.2 and Windows 7. I have ntfs-3g and have full read-write ability to my Windows drive through OpenSUSE thanks to NTFS - openSUSE. The only problem is whenever I write to the NTFS Windows drive via Dolphin it does the writing but I get an alert box saying: "Could not change permissions for <path to new file>" with an OK button. If I write more than one file I'll get one alert box for each file unless I don't press OK until after it finishes writing all the files in which case it will just give me that one that it was showing (once I press OK there aren't any more boxes). Since I have full ability to read-write this isn't that big of a problem it's just annoying as hell an I'm sure it's pretty simple to get rid of. code...
I told my friend ext3 and ext4 are very fragmentation resistant compared to ntfs and he questioned me as to what happens if a small file was removed from in between other file chunks and then another (larger) file was to be written and it wouldn't fit there; where would it go? His argument was that the ext filesystem does need to defragment in order to get past that and his argument seems logical. Does anyone know the answer to this? (because it actually captured my curiosity)
I heard that the ext file system does not causes file fragmentation. Could some one explain how this is achieved. And how come a file does not divides in to fragments as compared to Windows based Filesystems.
I have millions of small chunks of new's and delete's in my program. Even though no memory leak is detected through valgrind or purify, memory grows. But the growth is degrading over the number of times of the execution of the tasks. Can i think that fragmentation plays a role in this?
I work with lots of big files >500MB. As ext3 does not provide the extents feature of ext4, I am concerned that some fragmentation may periodically affect disk performance. Noted I understand that using ext4 under these circumstances would be pointless, because the extents feature would be required to be disabled to allow compatibility using ext2fsd at this time, thereby removing any tangible ext4 benefit for my purposes.
Question Would an effective method of disk optimisation and anti-fragmentation be to simply copy all files from the ext3 media partition across to another entirely separate empty backup ext3 drive, before copying them all back over to the ext3 media partition again? Would this mean that when all the files are copied back again, they would be placed back in the 'correct and optimum order', so to speak? PS: I cringe in advance at the n00bs who are likely to reply to this thread with 'ext3 cannot become fragmented'!
I am trying to write into a single log file from 3 different applications in C. In one of the applications I am forking out 5 instances. I would like to know what is the best way to open and close the log file in which i want to write from these applications. Should I open and close it at the start and end of each application or is it ok performance wise if i open and close it inside the log function which will be called for every write.
I've been trying to get Full Tilt Poker running for a while now, with the 32bit wine available for x86_64, but it complains about phonon4.dll not being able to initialize. I've tried using winetricks to get it working, since it's as good a starting point as any, but even if I do the program bails out on me constantly with:
winepath -u %ProgramFiles% returned empty stringles
I have fedora 13 64 bit installed on my desktop. I have i3-530, 2G ram, wd 500g sata, ide samsumg dvd-rw, asus h55 mb, geforce 9600 low profile. problem is f13 often almost always freezes at boot up.i.e., after grub, that blue heart hangs on there waiting to be filled up.. but wait forever. what might be the problem?
The best word that suits me to introduce is I am a novice! :-) but it is the difficult part get over with the new things and learnings!
Well once such situation made me introduce me to you is "Kernel Crash". I've recently installed Fedora 14 64 bit version on my HP HDX premium series, since then this Kernel crash is chasing me down! code...
I usually don't have problems installing Linux but Fedora won't install into 4 GB for me. I get to the partitioner, try to create a 4 GB partition, actually have 7 GB free, but it tells me there is no space on the drive. As I said, I usually don't get this problem but have not tried Fedora before and don't understand.
I downloaded Fedora-13-i686-Live.iso from the fedora project web site, and did the instruction on how to burn it using dvd. i used nero selecting burn a CD from an image file. after doing that, i restarted my laptop to install fedora 13 choosing to start the boot at the disk dvd but it won't boot to run the installation. instead the laptop will resume booting to its previously installed OS, fedora 9.
i browse the dvd media and there are 3 folders namely EFI, isolinux, LiveOS and GPL file.
It frozen up occasionally, when that happens, usually the harddisk light lights up continuously. So I suspect some process is writing to the disk, which prevent other process to go on. how do I find out who's using a lot of IO?
#! /bin/bash #SCRIPT FOR DISPLAYING INODE, FILE PERMISSIONS ETC OF COMMAND ARGUMENTS for data in $@ do
The sript above is executed:-
./script file1 file2 file3 file4 file 5...
The error is that instead of showing the inode etc, of the ALL FILES IN COMMAND LINE ARGUMENTS, THE SET COMMAND OF LINUX OVER WRITES THE $@, so only "ls -l' of 1st commadn argument(file1) is displayed. The script should display it for every file in linux directory.
I have installed LXDE recently and I'm very happy with it,but there's one problem,which is that i can't switch the keyboard layout to another language,which in my case is Arabic,how do i solve this problem?
I have a server installed with a Fedora 8 and the other client PC were installed with Windows XP. Recently, I copied an educational courseware (this courseware is developed specially for Windows based PC) into the Linux-based server. I found that the .EXE (application file) :were unable to be opened in all of the clients and also the server. How can I solve this problem?
When I installed fedora 11 I had bad sound which crackled and crashed. I followed this guide -http://forums.fedoraforum.org/showthread.php?t=225660 - which fixed my issues in videos playing on the web and in VLC. However; in the last few days sound has bugun crackling again in VLC while playing videos (web is fine). All updates have been applied and I am running 32 bit Fedora 11.
Also totem when playing video crashes, freezes, crackles etc while playing videos though playing sound files is fine with no issues. Any ideas how I might solve this and get my sound while playing videos back to how it used to be?