| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 11 Sep 2008 22:11:05 +0200 From: Harun Scheutzow <harun04@...eutzow.de> To: lsorense@...lub.uwaterloo.ca (Lennart Sorensen) Cc: linux-kernel@...r.kernel.org Subject: Re: vfat file system extreme fragmentation on multiprocessor At 21:10 11.09.2008, Lennart Sorensen wrote: Why do you start a flame war against fat fs without the proper knowledge? This is of no help. ext2 is no magic bullet. As any other file system which does not rearrange clusters on the fly (this is defragmentation), it can only prevent fragmentation by wasting space, that means it seems not to fragment at 25 % full, but does at 90 %, just depending on size of files created. Initially wasting space and on-the-fly defragmentation can be done on FAT as well, if the driver likes to do. All this NOT the problem here. It is NOT what I'm asking for. >Now what would happen if you used ftruncate to extend the file you open >to a large size, and then started writing it, and then set the size >correctly at the end? Because ftruncate has to allocate the clusters the same way fwrite does, it would probably give the same results. Anyway, I want to keep things simple. I do not know the final file size in advance, may be 550 MByte, often 200, but can be 5. It is perfectly ok to get 4 fragments per 200 MByte. All I suggest is that a file system which is told to write 50 MByte a piece, does so. I do not want to synchronize the two applications, preventing them from writing at the same time. But currently this seems to be the only option. Harun Scheutzow -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists