Re: ext4 - 52.2% non-contiguous

On Fri, Jul 10, 2009 at 02:29:10PM +0900, Miles Bader wrote: Actually shouldn't ext4 do _better_ (than ext3 etc) in such a case, since it does allocate-on-write, allowing it to allocate contiguous storage despite the user writes being small? Depends. If an application doesn't pre-allocate

Re: ext4 - 52.2% non-contiguous

Miles Bader mi...@gnu.org writes: Actually shouldn't ext4 do _better_ (than ext3 etc) in such a case, since it does allocate-on-write, allowing it to allocate contiguous storage despite the user writes being small? btw, I meant allocate-on-write-to-the-disk, aka delayed allocation... -Miles

Re: ext4 - 52.2% non-contiguous

On Mon, Jul 06, 2009 at 06:49:09PM -0400, Daryl Styrk wrote: After initially building the filesystem I ran fsck which showed something like 0.7% if I remember correctly. I then copied about 60GB from an ext3 via rsync after which the fragmentation showed up. by default, rsync copies a file

Re: ext4 - 52.2% non-contiguous

Todd A. Jacobs nos...@codegnome.org writes: by default, rsync copies a file in small chunks, so copying an entire filesystem to a drive that is actively in use could certainly cause fragmentation. Actually shouldn't ext4 do _better_ (than ext3 etc) in such a case, since it does

Re: ext4 - 52.2% non-contiguous

Daryl Styrk wrote: I'm trying to understand what is causing fsck to report /dev/sda4 being highly fragmented. The filesystem is only a couple days old. I created the it with mke2fs -t ext4. After initially building the filesystem I ran fsck which showed something like 0.7% if I remember

ext4 - 52.2% non-contiguous

I'm trying to understand what is causing fsck to report /dev/sda4 being highly fragmented. The filesystem is only a couple days old. I created the it with mke2fs -t ext4. After initially building the filesystem I ran fsck which showed something like 0.7% if I remember correctly. I then copied