Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
I tried to create an image (.img file) in the /root directory-logged in as root. /root has no partition of it's own; it's part of the / partition, which has 17,9 GB free. However, the image file is only going to be 10GB and the message i get is in the first 5 seconds, which means that even lesser space has been consumed.
Does /root has quota, or specific properties, which cause this problem?
Thank you FinalFantasy,
I searched and found, that in worst case (1kb block size) "ext2 or ext3" support 16GB files. I am also not sure, but it is implied, that for x86_64 files can be larger- i have an amd64.
I am speaking only from what I've read in forum posts before, not from fact or any documentation
I think /root does have a quota on it out of the box, or it reserves n% (not sure of the percentage) of the filesystem's free space so even if the disk is chock full, root can still log in. Not sure how this could play a part in your problem but it might be worth knowing
Originally posted by cs-cam I am speaking only from what I've read in forum posts before, not from fact or any documentation
I think /root does have a quota on it out of the box, or it reserves n% (not sure of the percentage) of the file-system's free space so even if the disk is chock full, root can still log in. Not sure how this could play a part in your problem but it might be worth knowing
There shouldn't be a quota out of the box, or if so, it should be cleared stated.
5% might be reserved by the file system. but it should not be the case in your situation.