Re: Does "32.1% non-contiguous" mean severely fragmented?

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Tetsuo Handa <penguin-kernel@...>
Cc: <linux-fsdevel@...>
Date: Tuesday, October 23, 2007 - 8:34 am

On Tue, Oct 23, 2007 at 07:38:20PM +0900, Tetsuo Handa wrote:

Or it may be that it takes a while to do a controlled shutdown.

One potential reason for the vmem file being very badly fragmented is
that it might not be getting written in sequential order.  If the
writer is writing the file in random order, then unless you have a
filesystem which can do delayed allocations, the blocks will get
allocated in the other that they are first written, and if the writer
is seeking to random locations to do the write, that's one way that
you can end up with a very badly fragmented file.

Regards,

							- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: Does "32.1% non-contiguous" mean severely fragmented?, Tetsuo Handa, (Fri Oct 19, 11:39 pm)
Re: Does "32.1% non-contiguous" mean severely fragmented?, Theodore Tso, (Tue Oct 23, 8:34 am)