I was not going to do the copies from a live system. I am going to mount
the target volume at /mnt and the source volume at some other point but I
think the tar method might be better.
As to the /usr and /var file systems being placed on to root.....
I've been asked to make 2 linux LPARS into 4 linux LPARS. Without using any
more disk than I currently am using. No VM (though that is finally going to
change)
Currently I'm using EKCD disk for everything. 4 mod 9's and 4 'custom' mod
3's per system
On the both systems I have root, /usr, /var and /opt each on their own mod
9. I have a custom volume (about a gig) used for swap and tmp. The other
two custom volumes per system were for LVM experimentation and this never
happened. After 4 years of light use, the one system has root at 9.08%
used, /var at 0.52% used, /usr at 11.81% used and /opt at 63.85% used.
System 2, the new one as of last fall has root at 0.75% used, /usr at 9.81%
used, /var at 0.359% used and opt at 8.36% used.
This entire structure is being built to accommodate WebSphere and DB2
connect EE. (DB2 connect EE is running on the system with the 68% opt,
along with the remains of this and that, that have been installed over the
years.
Since I do not see growth in /var and /usr statistically, nor do I expect
much growth because of the use of these systems, one way I could free up
enough dasd to make 2 more systems was to create a configuration where root
and /opt were on their own mod 9 which frees up 2 mod 9's per individual
system(which then allows a new root fs and /opt), and recycle the unused
custom volumes into swap and tmp for a new system, respectively.
Not doing this because I like it. I'm doing it because I've been told to do
so, and my calculations indicate that the combined root file systems will
be at 21.41% and 10.92% utilization respectively. Which should give me
enough room to breathe?
"Post, Mark K"
<[EMAIL PROTECTED]
m> To
Sent by: Linux on [EMAIL PROTECTED]
390 Port cc
<[EMAIL PROTECTED]
IST.EDU> Subject
Re: Copying an entire
filesystem.... and only that file
03/24/2004 03:25 system. B est tool?
PM
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
If you're going to be copying your root file system while the system is up
and running, I would not use dd for that. I would use the same method as
on
the HOWTO page on linuxvm.org. One of the switches on the first tar
command
says "stay within this file system." If you use dd, anything that is in
cache and not on disk won't be picked up.
Is there a reason why you want to have /var and /usr in your root file
system instead of where they're at now? Just on the face of it, I wouldn't
recommend it, but then I don't know what you're trying to accomplish.
If new DASD has been attached to the LPAR, you'll probably have to use the
service element to configure it online to the LPAR. Then, you should be
able to echo the "add device" command into /proc/dasd/devices. To keep
them
available, make sure to rebuilt your initrd (mkinitrd) if appropriate, and
re-run zipl.
Mark Post
-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of James
Melin
Sent: Wednesday, March 24, 2004 3:53 PM
To: [EMAIL PROTECTED]
Subject: Copying an entire filesystem.... and only that file system. Best
tool?
I am preparing to copy my root file system to another volume. If memory
serves, the best tool for that is dd? So it doens't traverse the rest of
the
mount points. That not withstanding what would people recommend to do the
following:
move root to a new volume and then copy two other file systems,
specifically
/var and /usr into the new copy of the root fs, effectively combining root
/var and /usr into the root fs space.
Secondly - if your sysprog dynacmicall adds a couple dasd devices to your
lpar environment that were not there, what is necesssary to make them
available to a running image? Is that possible or do I have to IPL?
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send email
to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
