On Mon, 13 Jun 2005, Alex Zbyslaw wrote:
Philip Hallstrom wrote:
I have a system that we are running in production that there was an
oversight on, and it has a single hard drive installed (32GB SCSI I
believe), rather than a 3 drive raid5 array. We would like to correct
this, but we have al
Philip Hallstrom wrote:
I have a system that we are running in production that there was an
oversight on, and it has a single hard drive installed (32GB SCSI I
believe), rather than a 3 drive raid5 array. We would like to
correct this, but we have all sorts of up-to-date packages and
config
I have a system that we are running in production that there was an
oversight on, and it has a single hard drive installed (32GB SCSI I
believe), rather than a 3 drive raid5 array. We would like to correct
this, but we have all sorts of up-to-date packages and config files that
we've tweaked t
Warren Block wrote:
On Fri, 10 Jun 2005, Tony Shadwick wrote:
I have a system that we are running in production that there was an
oversight on, and it has a single hard drive installed (32GB SCSI I
believe), rather than a 3 drive raid5 array. We would like to correct
this, but we have all so
Giorgos Keramidas wrote:
On 2005-06-10 12:47, Sarath ER <[EMAIL PROTECTED]> wrote:
This is how I do it on linux.. Correct me if I am wrong.
rsync -vrplogDtH /* /new
chroot and edit the fstab etc
I do not know how to fix the bootrecord in freebsd, please find howto.
# boot0cfg -v /de
Philip Hallstrom wrote:
Not that I do this a lot, but I think you'll run into problems using
tar, cp, and rsync when it comes to various special files or files with
holes in them (sparse files).
rsync should work just fine in archive mode (not sure what u mean by
sparse files though)
rs
On 2005-06-10 16:41, Tony Shadwick <[EMAIL PROTECTED]> wrote:
> Nope, everything is from ports. was just trying to avoide the 2+ days
> of compiling needed to rebuild everything. :(
Shutdown the system, install a new disk (or RAID of disks) and then move
over the data, as described in the followi
On 2005-06-10 12:47, Sarath ER <[EMAIL PROTECTED]> wrote:
> This is how I do it on linux.. Correct me if I am wrong.
>
> rsync -vrplogDtH /* /new
> chroot and edit the fstab etc
> I do not know how to fix the bootrecord in freebsd, please find howto.
# boot0cfg -v /dev/ad1
__
>
> You expect too much of my RAID controller. :) Ghost won't do it because:
>
> 1. There is only room for 3 drives in the system. RAID5 requires 3
> drives.
>
> 2. Ghost deals in partitions. FreeBSD (usually) has one partition with
> many slices.
Small, but important quibble if you are d
You expect too much of my RAID controller. :) Ghost won't do it because:
1. There is only room for 3 drives in the system. RAID5 requires 3
drives.
2. Ghost deals in partitions. FreeBSD (usually) has one partition with
many slices.
3. Doubt it has drivers for my RAID array. :)
On Fri,
Tony Shadwick wrote:
I have a system that we are running in production that there was an
oversight on, and it has a single hard drive installed (32GB SCSI I
believe), rather than a 3 drive raid5 array. We would like to correct
this, but we have all sorts of up-to-date packages and config fi
Philip Hallstrom on 2005-06-10 14:07:28 -0700:
> Then somewhere else I have an NFS server running. Mount the share on your
> live CD box. dump each partition to the share.
If you're going to take this approach, nothing is simpler than g4u.
g4u is wonderful.
pgp8wK2xR03Js.pgp
Description: PGP
On Fri, 10 Jun 2005, Tony Shadwick wrote:
I have a system that we are running in production that there was an oversight
on, and it has a single hard drive installed (32GB SCSI I believe), rather
than a 3 drive raid5 array. We would like to correct this, but we have all
sorts of up-to-date pac
Nope, everything is from ports. was just trying to avoide the 2+ days of
compiling needed to rebuild everything. :(
On Fri, 10 Jun 2005, Haulmark, Chris wrote:
Someone broke the silence:
Except that I still have to re-install all of the packages in
/usr/local, many which have been built fro
Here's my scenario:
I have a system that we are running in production that there was an oversight
on, and it has a single hard drive installed (32GB SCSI I believe), rather
than a 3 drive raid5 array. We would like to correct this, but we have all
sorts of up-to-date packages and config files
Someone broke the silence:
> Except that I still have to re-install all of the packages in
> /usr/local, many which have been built from sources. or are you
> suggesting that I
> copy out the /usr/local tree as well? Will that break anything?
>
Well, you brought up something that I forgot ab
Except that I still have to re-install all of the packages in /usr/local,
many which have been built from sources. or are you suggesting that I
copy out the /usr/local tree as well? Will that break anything?
On Fri, 10 Jun 2005, Haulmark, Chris wrote:
Someone broke the silence:
Here's my
Someone broke the silence:
> Here's my scenario:
>
> I have a system that we are running in production that there was an
> oversight on, and it has a single hard drive installed (32GB SCSI I
> believe), rather than a 3 drive raid5 array. We would like
> to correct
> this, but we have all sorts
This is how I do it on linux.. Correct me if I am wrong.
rsync -vrplogDtH /* /new
chroot and edit the fstab etc
I do not know how to fix the bootrecord in freebsd, please find howto.
boot from the array
lets hope this helps.
- Sarath
Tony Shadwick wrote:
Here's my scenario:
I have a system
19 matches
Mail list logo
