Linode Forum
Linode Community Forums
 FAQFAQ    SearchSearch    MembersMembers      Register Register 
 LoginLogin [ Anonymous ] 
Post new topic  Reply to topic
Author Message
PostPosted: Fri Sep 12, 2003 1:31 am 
Offline
Junior Member

Joined: Fri Sep 12, 2003 12:58 am
Posts: 26
Website: http://www.symetrix.com
I would like the ability to setup a disk image that I can use as a base image for testing. That way I can boot a cloned copy of my drive image, trash it, then start over (my requirements are probably a lot different than some users).

I can of course write a script that "customizes" the distro image, but I'd rather customize it one, then clone it when I need it.

Also, UML has the ability to use COW files (copy on write). Should I assume that behind the scenes that's what you're using to reduce the disk space used by each distro created? If not, the ability to manage COW files would be real handy and a great alternative cloning.


Top
   
PostPosted: Fri Sep 12, 2003 11:05 am 
Offline
Senior Member

Joined: Sat Jun 28, 2003 12:02 am
Posts: 66
Website: http://kenny.aust.in
bjohnson wrote:
I would like the ability to setup a disk image that I can use as a base image for testing. That way I can boot a cloned copy of my drive image, trash it, then start over (my requirements are probably a lot different than some users).


Create a new partition with enough space, boot into single user mode and
Code:
cp -a -x / /mnt/ubdx
it's always worked for me.

kenny


Top
   
 Post subject:
PostPosted: Fri Sep 12, 2003 11:53 am 
Offline
Linode Staff
User avatar

Joined: Tue Apr 15, 2003 6:24 pm
Posts: 3090
Website: http://www.linode.com/
Location: Galloway, NJ
There are a few things one needs to watch out for with COW files, but the biggest issue is that the backing-file (the distro) and the COW file's image size needs to be pre-set. So, if I wanted an 800 MB Red Hat Disk Image I'd need a backing file for that. If someone wanted a 2GB RH Image, i'd need a backing file for that, too. And so on.

COW would work really well for your situation. There is a small amount of COW support already in my system, although I decided against using it for the main installs.

I think for now the best method is just the mount; copy method.

-Chris


Top
   
 Post subject:
PostPosted: Fri Sep 12, 2003 2:57 pm 
Offline
Junior Member

Joined: Fri Sep 12, 2003 12:58 am
Posts: 26
Website: http://www.symetrix.com
I have no experience actually doing this, so this may be a stupid question... Why does the COW file size have to be preset? It seems like the documentation implies that it can be created dynamically on boot by specifying the COW file on the command line:

http://user-mode-linux.sourceforge.net/ ... html#ss7.7

Or is this a requirement of the linode system?


Top
   
 Post subject:
PostPosted: Fri Sep 12, 2003 3:37 pm 
Offline
Linode Staff
User avatar

Joined: Tue Apr 15, 2003 6:24 pm
Posts: 3090
Website: http://www.linode.com/
Location: Galloway, NJ
The COW file inherits whatever size the backing file is. It might not actually take up more space on the disk (at first) than the backing file, but the issue is that everyone creates a different size "image", and you must have backing files for each different size.

There's no way to have a COW file give you more space than whatever size the backing file is.

-Chris


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic


Who is online

Users browsing this forum: No registered users and 0 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
RSS

Powered by phpBB® Forum Software © phpBB Group