Good question Benjamin,
>From my experience with ext2 on my systems, I have never seen significant 
fragmentation on ext2 when if was less than 80% full, but this is not 
really empiracle  evidence. However, I was very disappointed with NTFS. I 
have found on my Windows 2000 system at work the need to defragment almost 
immediately after an install.
I think that part of the difference is that Linux buffers all of its I/O 
where NT systems do not (AFAIK).
Benjamin Scott wrote:

>   Does anyone know of any unbiased and current analysis of this issue?  The
> information in that HOWTO is rather biased, and contains the out-of-date
> assumption that multi-hundred-gigabyte filesystems are unlikely.  It
> basically answers the question of "Does ext2 suffer from fragmentation
> issues?" with "No, because MS-DOS sucks."  While I agree with the author's
> sentiments, they do not support the conclusions.  At the same time, NTFS
> supposedly has a much better design, and analysis of *it* has shown that
> fragmentation *is* still an issue for some applications.  Has anyone
> actually tested ext2 for this, or are we just happy living in dreamland?
> 
> -- 
> Ben Scott <[EMAIL PROTECTED]>
> | The opinions expressed in this message are those of the author and do not |
> | necessarily represent the views or policy of any other person, entity or  |
> | organization.  All information is provided without warranty of any kind.  |
> 
> 
> *****************************************************************
> To unsubscribe from this list, send mail to [EMAIL PROTECTED]
> with the text 'unsubscribe gnhlug' in the message body.
> *****************************************************************
> 

-- 
Jerry Feldman <[EMAIL PROTECTED]>
Boston Linux and Unix user group
http://www.blu.org PGP key id:C5061EA9
PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9



*****************************************************************
To unsubscribe from this list, send mail to [EMAIL PROTECTED]
with the text 'unsubscribe gnhlug' in the message body.
*****************************************************************

Reply via email to