OK, did some research and here's what I found:
According to a Wikipedia entry, EXT2 (ReiserFS) has a built in
tail-packing scheme "to reduce internal file fragmentation. Tail packing, however, has a significant performance impact; Namesys recommends disabling the feature in performance-critical applications."
So digging further, you find that there is external fragmentation (like what I described above) and there is internal fragmentation. Internal is described by Wiki as "...any space left over between the last byte of the file and the first byte of the next sector..."
So what does all that mean? It means that ReiserFS is not immune to fragmentation. It only has a built-in feature to handle "slack space" (
internal frag) issues, which NameSys admits causes a noticeable hit on performance. Holes with free space like in the example I mentioned will undoubtedly cause external fragmentation, even in ReiserFS.
But here's the kicker you were probably taught. According to the article below, most fragmentation in ReiserFS does not matter [blue]
when paired with the Linux OS[/blue]. This is because Linux reads ahead 16 blocks. The ext2 file system in turn writes files using at least 7 successive blocks. The combination of style that Linux and ext2 use in reading/writing data cancels out the effect of MOST fragmentation.
The bottom line is that ReiserFS gets fragmented just like other file systems. It just doesn't impact performance in the same way that it does in FAT or FAT32 for example.
~cdogg
"
Insanity: doing the same thing over and over again and expecting different results." - Albert Einstein
[tab][navy]For general rules and guidelines to get better answers, click here:[/navy] faq219-2884