G4U inquiry

2008-12-04 Thread Jean-Paul Natola
Hi all,

I have a bsd box with a 12 gig drive- I'm going to get a new drive (larger)
to replace it as it is quite old and slow -

My question is when I clone it with g4u  where will the extra space go

The drive is currently sliced like this

Filesystem SizeUsed   Avail Capacity  Mounted on
/dev/ad0s1a496M 76M381M17%/
devfs  1.0K1.0K  0B   100%/dev
/dev/ad0s1e496M 11M445M 3%/tmp
/dev/ad0s1f9.0G1.4G6.8G17%/usr
/dev/ad0s1d1.4G301M1.0G22%/var


tia
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: G4U inquiry

2008-12-04 Thread Tyson Boellstorff
On Thursday 04 December 2008 14:44:40 Jean-Paul Natola wrote:

 I have a bsd box with a 12 gig drive- I'm going to get a new drive (larger)
 to replace it as it is quite old and slow -

 My question is when I clone it with g4u  where will the extra space go


it's in the faq.

http://www.feyrer.de/g4u/#disks

5.4 A word on disk sizes

  The question how g4u deals with different disk sizes arises a lot too. 
The general answer is, g4u works best with identical disk sizes  geometry. 
Putting an image from a small disk on a big disk works, putting an image from 
a big disk to a small disk is likely to cause problems.

  If you cannot avoid preparing an image on a big disk that'll get 
deployed to a small disk later, make sure the extra space is not occupied 
by a active partition or filesystem, else data loss is very likely to occur!

  If you intend to deploy a small image to a big disk, the extra space 
that's not covered by g4u can be used for creating a partition and a 
filesystem. You will have to do that on your own, e.g. using your operating 
systems' post installation steps. 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: G4U inquiry

2008-12-04 Thread Wojciech Puchar

I have a bsd box with a 12 gig drive- I'm going to get a new drive (larger)
to replace it as it is quite old and slow -

My question is when I clone it with g4u  where will the extra space go


why not simply partition new drive and copy everything?

or use dd and then correct partiiton table

unix has tools for this, much simpler much better and included ;)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: G4U inquiry

2008-12-04 Thread Jerry McAllister
On Thu, Dec 04, 2008 at 03:00:09PM -0600, Tyson Boellstorff wrote:

 On Thursday 04 December 2008 14:44:40 Jean-Paul Natola wrote:
 
  I have a bsd box with a 12 gig drive- I'm going to get a new drive (larger)
  to replace it as it is quite old and slow -
 
  My question is when I clone it with g4u  where will the extra space go
 

 
Usually you are much better off creating new [slices and] partitions
with new appropriate sizes, newfs-ing the partitions to turn them in
to filesystems and then copying the previous disk filesystem by filesystem 
to the new disk - using dump/restore.Then you will not be stuck with
geometry mismatches and wasted disk space. I have posted excruciatingly
detailed instructions for this sort of things about every coupld of months
on this list as other have asked.A little searching should find one.
If not, I can give a basic rundown.

jerry



 
 it's in the faq.
 
 http://www.feyrer.de/g4u/#disks
 
 5.4 A word on disk sizes
 
   The question how g4u deals with different disk sizes arises a lot too. 
 The general answer is, g4u works best with identical disk sizes  geometry. 
 Putting an image from a small disk on a big disk works, putting an image from 
 a big disk to a small disk is likely to cause problems.
 
   If you cannot avoid preparing an image on a big disk that'll get 
 deployed to a small disk later, make sure the extra space is not occupied 
 by a active partition or filesystem, else data loss is very likely to occur!
 
   If you intend to deploy a small image to a big disk, the extra 
 space 
 that's not covered by g4u can be used for creating a partition and a 
 filesystem. You will have to do that on your own, e.g. using your operating 
 systems' post installation steps. 
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]