FedoraThis forum is for the discussion of the Fedora Project.
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.
Based on response to an earlier question I posted re. backup of LVMs, I stepped back and installed FC5 on manually specified ext3 partitions, no LVM. I can now image and restore with partimage. However, Norton Ghost 2003 and Acronis True Image still fail. My research has led me to the following change which occurred with FC3 - just when the trouble began. From the FC3 release notes:
The ext2online utility has been added for online growing of existing ext3 file systems.
It is important to keep in mind that ext2online does not grow the underlying block device itself — there must be sufficient unused space already present on the device. The easiest way to ensure this is to use LVM volumes and to run lvresize or lvextend to extend the device.
In addition, file systems must be specially prepared in order to be resized past a certain point. The preparation involves reserving a small amount of space into which on-disk tables can grow. For newly-created file systems, mke2fs reserves such space automatically; the space reserved is sufficient to grow the file system by a factor of 1000. The creation of this reserved space can be disabled by the following command:
mke2fs -O ^resize_inode"
So my question is... how do I disable this resize inodes DURING INSTALL of FC5? I can manually specify the partitions however I do not find any option re. inodes. I always specify a fixed size for the partition so that does not seem to be the trick.
Which brings to mind a second question - how do I know if I have resize inodes on a particular FS? Perhaps the fixed size has done the trick and my image issue is something else.
To disable the creation of resize inodes, you need to partition and format before installation, and tell anaconda (the Fedora/Redhat installation program) not to format the existing partitions it is installing onto. You can check existing partitions with: