SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Hi all! Recently I've downloaded the new X.org source and right after that, even after installing and removing the source directory, the 'df' commmand has been confusing me about the amount of free space I have left on my disk. The output of it:
Filesystem Size Used Avail Use% Mounted on
/dev/hdb2 5.7G 5.1G 250M 96% /
Shouldn't I have like 600M available? Is there any distinction between non-used and available space? If so, then how can I make all my non-used space available?
Is your filesystem ext2 or ext3 ?
If yes - when you created it with the default options,like:
mkfs.ext3 -j /dev/hdaX
it reserves 5% of the space solely for the super-user aka: root - and consequently does not show this space in "df" even if it is there - but just for "root" to be able to log in and do maintanance even if somehow the filesysten got completely full.
Today, with the help of a live-cd this is easy to do from "outside" - so, for a pretty much "single user" desktop-system there is no need to reserve that much space just in case.
mkfs.ext3 -j -m 0 /dev/hdX
will set the amount of reserved space to 0 for example - that is what I have done on my system
Is your filesystem ext2 or ext3 ?
If yes - when you created it with the default options,like:
mkfs.ext3 -j /dev/hdaX
it reserves 5% of the space solely for the super-user aka: root - and consequently does not show this space in "df" even if it is there - but just for "root" to be able to log in and do maintanance even if somehow the filesysten got completely full.
Today, with the help of a live-cd this is easy to do from "outside" - so, for a pretty much "single user" desktop-system there is no need to reserve that much space just in case.
mkfs.ext3 -j -m 0 /dev/hdX
will set the amount of reserved space to 0 for example - that is what I have done on my system
Good info. But that would be when he is creating the filesystem right ? Since his filesystem is already created and in place, is there any way to adjust without losing/corrupting data ?
Only from "outside" - a live-cd like knoppix or the install cd...
the filesystem in question needs to be NOT mounted...
He could run: tune2fs -m 0 -o journal_data -O dir_index,sparse_super /dev/hdaX
followed by: fsck.ext3 -f -D /dev/hdaX
...to re-index the filesystem - to optimize the filesystem to use the hashed b-trees option of ext3 / ext2 - which is faster than the default.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.