Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • ok, that clears it pretty much. thank you! a statement like if you run for long periods of time (with lots of file creates and deletes) while the filesystem is almost full (i.e., say above 95%), at which point you'll be subject to fragmentation problems. is exactly what I was looking for. Commented Apr 19, 2011 at 14:52
  • But let's be clear: ext3 fragmentation isn't at all the same as NTFS fragmentation. ext3 allocates disk blocks to files as individual blocks. NTFS allocates disk blocks in extents. A "fragmented" NTFS file can have multiple inode-equivalents full of very small extents of disk blocks. Commented Apr 19, 2011 at 16:18
  • @boehj Can you explain a little on how you decided on the amount of blocks reserved (20000) for root when the drive is primarily used for storage? Is that something that is relative to the size of the drive, amount of files, file sizes, etc? Commented Aug 21, 2012 at 21:44
  • Actually I can't really. I used that example because when I learnt about the process, that was the example quoted in the guide. And subsequent to that I've used this number on quite a few systems and had no problems. Perhaps someone else can add some info? Commented Aug 22, 2012 at 12:24
  • @boehj Dang, I was trying to figure it out because I'm not sure if you need to change the size relative to the HD size; does a 1TB HD need more space than a 100GB HD/Partition or does it depend on the disk usage (storage, root fs, home, boot, etc...) Commented Aug 27, 2012 at 18:18