mv hard drives with lvm/selinux ?

[Justin Conover]

Just wondering if i'm going to move 2x160GB sata drives in raid 1 that
are on there own volume with SELinux turned on.  Can I simply move
these to another box and be able to read them or does this become
really tricky?

Worst comes to worst I can mv the 80GB of data to another box, mv the
harddrives and then mv the data back just wondering if it could be as
easy to do it the other way.

[Colin Walters]

On Tue, 2005-03-08 at 11:53 -0600, Justin Conover wrote:
>  Just wondering if i'm going to move 2x160GB sata drives in raid 1
> that
>  are on there own volume with SELinux turned on.  Can I simply move
>  these to another box and be able to read them or does this become
>  really tricky? 
If you use mv, cp -a --preserve=all, or rsync -X, security contexts of
files should be preserved.  

However, if you have a default FC3 install you're already using LVM, you
might consider simply placing the raid device as part of your existing
volume group, and not worrying about copying/moving data around.  At
least if it works to do RAID under LVM :)

[Justin Conover]

I might not have to move the box after all, so I can put this test off
for now.  Thanks for your input though.


On Tue, 08 Mar 2005 13:23:13 -0500, Colin Walters <walters(a)redhat.com&gt; wrote:
>  On Tue, 2005-03-08 at 11:53 -0600, Justin Conover wrote:
>  > Just wondering if i'm going to move 2x160GB sata drives in raid 1 that
>  > are on there own volume with SELinux turned on.  Can I simply move
>  > these to another box and be able to read them or does this become
>  > really tricky?
>  
>  If you use mv, cp -a --preserve=all, or rsync -X, security contexts of
>  files should be preserved.
>  
>  However, if you have a default FC3 install you're already using LVM, you
>  might consider simply placing the raid device as part of your existing
>  volume group, and not worrying about copying/moving data around.  At
>  least if it works to do RAID under LVM :)
>  
>

[Justin Conover]

This kind of brings up another question, if I create a raid 5 with 3
or 4 disk and have my system only one 1 disk, and that one disk blows
up.  Will it be easy to replace that disk and see the
raid5/lvm/selinux files?  Or should I take the caution and put my
system in a raid 1 too.

thx


On Wed, 9 Mar 2005 07:16:56 -0600, Justin Conover
<justin.conover(a)gmail.com&gt; wrote:
>  I might not have to move the box after all, so I can put this test
> off
>  for now.  Thanks for your input though.
>  
>  
>  On Tue, 08 Mar 2005 13:23:13 -0500, Colin Walters <walters(a)redhat.com&gt; wrote:
>  > On Tue, 2005-03-08 at 11:53 -0600, Justin Conover wrote:
>  > > Just wondering if i'm going to move 2x160GB sata drives in raid 1 that
>  > > are on there own volume with SELinux turned on.  Can I simply move
>  > > these to another box and be able to read them or does this become
>  > > really tricky?
>  >
>  > If you use mv, cp -a --preserve=all, or rsync -X, security contexts of
>  > files should be preserved.
>  >
>  > However, if you have a default FC3 install you're already using LVM, you
>  > might consider simply placing the raid device as part of your existing
>  > volume group, and not worrying about copying/moving data around.  At
>  > least if it works to do RAID under LVM :)
>  >
>  >
>

[Russell Coker]

On Sunday 13 March 2005 02:07, Justin Conover <justin.conover(a)gmail.com&gt; 
wrote:
>  This kind of brings up another question, if I create a raid 5 with 3
>  or 4 disk and have my system only one 1 disk, and that one disk blows
>  up.  Will it be easy to replace that disk and see the
>  raid5/lvm/selinux files?  Or should I take the caution and put my
>  system in a raid 1 too. 
With some effort you can have grub boot from a RAID-1 (I won't try to explain 
how as I'm not an expert on booting, but it's something I've done before).

You may decide to use non-RAID for /boot.  After the kernel and the initrd 
have been loaded the initrd can setup RAID so you can have LVM on software 
RAID for the root file system (it's even supported in Anaconda).

For a serious machine there are two ways of doing it.  One is to have RAID for 
all file systems including the root file system.  The other option is to have 
a kickstart configuration that completely describes the configuration of the 
system so that the machine can easily be reinstalled at a moment's notice.

For an ideal server room you would have RAID on the system partitions and swap 
(so that a disk dying won't cause you to do any work at 3AM), RAID for data 
partitions (of course!), as well as having a dedicated server for kickstart 
that does DHCP and has NFS read-only shares containing every version of 
RHEL/Fedora that you run on your network.  To do this right the kickstart 
server would be configured to assign a particular IP address and config file 
to each machine based on it's MAC address so reinstalling any server could be 
done by merely booting from a kickstart device (either CD or USB dongle).

One thing I'm working on at the moment is a document on kickstart 
configuration for SE Linux.

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page

[Justin Conover]

On Apr 12, 2005 1:20 AM, Russell Coker <russell(a)coker.com.au&gt; wrote:
>  On Sunday 13 March 2005 02:07, Justin Conover
> <justin.conover(a)gmail.com&gt;
>  wrote:
>  > This kind of brings up another question, if I create a raid 5 with 3
>  > or 4 disk and have my system only one 1 disk, and that one disk blows
>  > up.  Will it be easy to replace that disk and see the
>  > raid5/lvm/selinux files?  Or should I take the caution and put my
>  > system in a raid 1 too.
>  
>  With some effort you can have grub boot from a RAID-1 (I won't try to explain
>  how as I'm not an expert on booting, but it's something I've done before).
>  
>  You may decide to use non-RAID for /boot.  After the kernel and the initrd
>  have been loaded the initrd can setup RAID so you can have LVM on software
>  RAID for the root file system (it's even supported in Anaconda).
>  
>  For a serious machine there are two ways of doing it.  One is to have RAID for
>  all file systems including the root file system.  The other option is to have
>  a kickstart configuration that completely describes the configuration of the
>  system so that the machine can easily be reinstalled at a moment's notice.
>  
>  For an ideal server room you would have RAID on the system partitions and swap
>  (so that a disk dying won't cause you to do any work at 3AM), RAID for data
>  partitions (of course!), as well as having a dedicated server for kickstart
>  that does DHCP and has NFS read-only shares containing every version of
>  RHEL/Fedora that you run on your network.  To do this right the kickstart
>  server would be configured to assign a particular IP address and config file
>  to each machine based on it's MAC address so reinstalling any server could be
>  done by merely booting from a kickstart device (either CD or USB dongle).
>  
>  One thing I'm working on at the moment is a document on kickstart
>  configuration for SE Linux.
>  
>  --
>  http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
>  http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
>  http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
>  http://www.coker.com.au/~russell/  My home page
>   
Kickstart for SELInux would  be great :D

I did get the box up with 2x40GB drives fro /boot everything else
under /lvm with seperate slices in raid 1 and 4x160GB drives in a raid
5 for /home