Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Noncontiguous placement of blocks in a file is bad for performance, since
files are often accessed in a sequential manner. It forces the operating
system to split a disk access and the disk to move the head. This is called
"external fragmentation" or simply "fragmentation" and is a common problem
with MS-DOS file systems. In conjunction with the abysmal buffer cache used
by MS-DOS, the effects of file fragmentation on performance are very
noticeable. DOS users are accustomed to defragging their disks every few
weeks and some have even developed some ritualistic beliefs regarding
None of these habits should be carried over to Linux and ext2. Linux native
file systems do not need defragmentation under normal use and this includes
any condition with at least 5% of free space on a disk. There is a
defragmentation tool for ext2 called defrag, but users are cautioned against
casual use. A power outage during such an operation can trash your file
system. Since you need to back up your data anyway, simply writing back from
your copy will do the job.
I'm sure this applies to other Linux filesystems as well.
Well, I agree that there is no apparent need for defragmentation under ext2/ext3 filesystems...But, I can think of a situation where defragmentation becomes significant...and that is, when one wants to reduce the size of a partition....If the data is fragmented, reducing partition size may result in data loss...So if there was a decent defragmentation tool for linux based filesystems, we could carry out the resizing operation more confidently.......what do u guys think about that?
i think mybe you got yourself a project?, lol, and yea that should aply to other linux file systems, sence there not half as'ed like msdos's are, but there what? 4 main linux file systems concirered "native" then you got like otheres , like 12 or so you can use (like FS used on macs, or windows (i dono about ntfs write suport tho, i havent switched to the new kernel as i dont wanna waste tiem gathering up all the patches again, call me lazy)
Excellent idea. I did not know you could lose data if you resized your partition. I thought it would stop you to the point of the last info. But even this could pose a problem and not allow you to resize to a desired point.