Page 2 of 2

Posted: Mon Apr 10, 2006 1:58 pm
by Troy McClure
Yeah, I actually saw that. I ended up getting a new server (needed to upgrade), so I can kind of "test" the image before I use it. Thanks for the heads up though.

Posted: Tue Apr 11, 2006 2:17 pm
by Troy McClure
Well, I got a new server and am attempting to repartition it, but have run into a problem. When I go do the tar as you explained I see all directories going in, but when I try to untar it, it will just stop and not all files are extracted. These are the last few lines of the process.

sys/block/
sys/block/md0/
sys/block/md0/md/
sys/block/md0/md/new_dev
sys/block/md0/md/metadata_version
sys/block/md0/md/component_size
sys/block/md0/md/chunk_size
sys/block/md0/md/raid_disks

I don't get an error or anything, but not all files are there. Any idea as to what is going on? It doesn't continue after this, so I am missing quite a lot of data. Thanks.

Posted: Tue Apr 11, 2006 5:45 pm
by scott
Yeah I'll have to try that myself this weekend, there is an alternative method using parted to resize the file system on the fly. I tried that with FC2, but ran into some issues with xfs partitions, you can only tinker with those so much before parted complains.

Posted: Wed Apr 12, 2006 11:13 am
by Troy McClure
I read an article that explains how to upgrade a drive and they used the l flag when tarring the files. It leaves off the data in the /sys /tmp and /proc directories. Would this work if that data was left off? I can do a tar by using
tar lzcvfp /var/backup.tar.gz / /usr /home /var
You have to add the other partitions when doing it this way. When I untar this everything is there except the file are not in /sys /tmp and /proc. Could this work?