Jerry57
2005-Dec-16 14:09 UTC
[CentOS] Ghost 8.0 Clone Filesystem with ext3 (remove resize_inode and ext_attr features)
Try using Acronis True Image or G4U (Ghost 4 Unix), I have had really good luck with both. Imaged both CentOS only or dual boot machines without out error. Norton/Symantec doesn't seem to care about Linux/Unix systems anymore, so I have switched for all of my back/image needs. jer Cesar Lagarrigue wrote:> I've Found a page with interesing discussion about images backup > > http://forums.fedoraforum.org/archive/index.php/t-28255.html > > This give a "dirty" solucion for remove special thing of ext3 (Selinux > remove resize_inode and ext_attr features) witch cause the error in ghost. > > I hope somebody help with the problem of norton ghost and clone centos 4. > > :) > > ----------- > > sfabkk > 2005-07-11, 04:53 AM PDT > Solution to using Ghost 8 with Core 3 and 4 > Good news : It can be done > > Bad News : You have to turn off SELinux Forever and remove resize_inode > and ext_attr features > from filesystem. Also if you mess this up it could kill your system, so > I would use G4U (Ghost 4 Unix) to image it first before you try. > > Here's the procedure to remove resize_inode and ext_attr features > from filesystems on an FC3 or FC4 installation. Everything must be done > from > the root account. > > Step 1 > > If you installed FC3 or FC4 with SELinux enabled, which is the default, it > you must disabled. Log on the system and edit /etc/selinux/config. > Replace SELINUX=enforced by SELINUX=disabled. If you don't disable > SELinux, the ext_attr will be set again on the root filesystem the > next time you boot and every file created or modified will have its > extended ACL entries set. > > Step 2 > > Download e2fsprogs-1.36-rc5 from SourceForge. Click on the following > link: > > http://sourceforge.net/projects/e2fsprogs > > Step 3 > > Untar, compile and install the new utilities: > > tar -zxf e2fsprogs-1.36-rc5.tar.gz > cd e2fsprogs-1.36-rc5 > ./configure > make > make install > > Step 4 > > Reboot the system in single-user mode: > > type reboot > > at the GRUB splash screen, press enter then press the 'a' and > add the word single at the end of the command line (there's a space > between quiet and single) > > Step 5 > > Unmount all filesystems, including /, and remove both resize_inode > and ext_attr features. Run the following commands on all filesystems: > > debugfs -w /dev/XXXX -R "features ^resize_inode ^ext_attr" > e2fsck -y -f /dev/XXXX > > Example: > > /dev/sda1 is mounted on /boot > /dev/sda2 is mounted on / > /dev/sda5 is mounted on /home > > umount /boot > umount / > umount /home > > debugfs -w /dev/sda1 -R "features ^resize_inode ^ext_attr" > debugfs -w /dev/sda2 -R "features ^resize_inode ^ext_attr" > debugfs -w /dev/sda5 -R "features ^resize_inode ^ext_attr" > > e2fsck -y -f /dev/sda1 > e2fsck -y -f /dev/sda2 > e2fsck -y -f /dev/sda5 > > Running e2fsck on the root filesystem takes a while. > > Step 6 > > Reboot the system. > > During shutdown, you will get error messages telling you that the > root filesystem cannot be written. That's normal because the root > filesystem is still mounted read-only. It must remain mounted read- > only during shutdown. > > During boot, you will get a message telling you that the system was > not properly shutdown and ask you if you want to verify the > filesystem integrity. You can skip this step. It didn't find anything > wrong on my system. > > Your system is now ready to be Ghosted. > > link to the bugzilla report > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145307 > > > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos-- Windows has detected that your mouse has moved, please wait while Windows reboots for your changes to take effect. This is Linux Country. On a quiet night, you can hear Windows reboot.
Cesar Lagarrigue
2005-Dec-16 14:57 UTC
[CentOS] Ghost 8.0 Clone Filesystem with ext3 (remove resize_inode and ext_attr features)
I've Found a page with interesing discussion about images backup http://forums.fedoraforum.org/archive/index.php/t-28255.html This give a "dirty" solucion for remove special thing of ext3 (Selinux remove resize_inode and ext_attr features) witch cause the error in ghost. I hope somebody help with the problem of norton ghost and clone centos 4. :) ----------- sfabkk 2005-07-11, 04:53 AM PDT Solution to using Ghost 8 with Core 3 and 4 Good news : It can be done Bad News : You have to turn off SELinux Forever and remove resize_inode and ext_attr features from filesystem. Also if you mess this up it could kill your system, so I would use G4U (Ghost 4 Unix) to image it first before you try. Here's the procedure to remove resize_inode and ext_attr features from filesystems on an FC3 or FC4 installation. Everything must be done from the root account. Step 1 If you installed FC3 or FC4 with SELinux enabled, which is the default, it you must disabled. Log on the system and edit /etc/selinux/config. Replace SELINUX=enforced by SELINUX=disabled. If you don't disable SELinux, the ext_attr will be set again on the root filesystem the next time you boot and every file created or modified will have its extended ACL entries set. Step 2 Download e2fsprogs-1.36-rc5 from SourceForge. Click on the following link: http://sourceforge.net/projects/e2fsprogs Step 3 Untar, compile and install the new utilities: tar -zxf e2fsprogs-1.36-rc5.tar.gz cd e2fsprogs-1.36-rc5 ./configure make make install Step 4 Reboot the system in single-user mode: type reboot at the GRUB splash screen, press enter then press the 'a' and add the word single at the end of the command line (there's a space between quiet and single) Step 5 Unmount all filesystems, including /, and remove both resize_inode and ext_attr features. Run the following commands on all filesystems: debugfs -w /dev/XXXX -R "features ^resize_inode ^ext_attr" e2fsck -y -f /dev/XXXX Example: /dev/sda1 is mounted on /boot /dev/sda2 is mounted on / /dev/sda5 is mounted on /home umount /boot umount / umount /home debugfs -w /dev/sda1 -R "features ^resize_inode ^ext_attr" debugfs -w /dev/sda2 -R "features ^resize_inode ^ext_attr" debugfs -w /dev/sda5 -R "features ^resize_inode ^ext_attr" e2fsck -y -f /dev/sda1 e2fsck -y -f /dev/sda2 e2fsck -y -f /dev/sda5 Running e2fsck on the root filesystem takes a while. Step 6 Reboot the system. During shutdown, you will get error messages telling you that the root filesystem cannot be written. That's normal because the root filesystem is still mounted read-only. It must remain mounted read- only during shutdown. During boot, you will get a message telling you that the system was not properly shutdown and ask you if you want to verify the filesystem integrity. You can skip this step. It didn't find anything wrong on my system. Your system is now ready to be Ghosted. link to the bugzilla report https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145307 -- Cesar Lagarrigue V. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 4097 bytes Desc: S/MIME Cryptographic Signature URL: <http://lists.centos.org/pipermail/centos/attachments/20051216/828b9ba3/attachment-0001.bin>
Seemingly Similar Threads
- Ext3 filesystem access after downgrade from v4.2 to v3.6 [SOLVED]
- ext3 incompatability between linux 2.4/ppc and linux 2.6/x86
- clone RHEL 4 ext3 partition
- FC5: "ext_attr" and "large_file" features for ext3 file systems ???
- [RFC] mke2fs with DIR_INDEX, RESIZE_INODE by default