On Thu, Apr 8th, 2010 at 4:58 AM, Ron Foster wrote:
> The DBAs cancelled the DB2 thread. The SAP Administrators issued all the
> commands thru
> SAP to get rid of the process. They did not work. The process did not
> go away. Then we tried a kill -9 and the process died.
>
> On the other two
We're looking at a storage frame migration and considering which
methods to use. We have LUNs as PVs in LVM, with one or more LVs
defined for each volume group. What is best practice to move to new
sets of luns?
Some methods which come to mind are ...
rsync (of filesystem content)
I used the "add the new PVs and delete the old (and let LVM migrate the
extents)" method to move off dasd and it worked well. If you can't take the
filesystems down the method has the advantage of no downtime, and LVM moves
only the used PE's (physical extents) not the unused ones. Try it on a t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Folks:
A few of you may remember me lamenting the unavailability of low cost
z/VM hobbiest installations a while ago.
Turns out there's a company trying to commercialize the Hercules
emulator, although not precisely for my pet usecase. Said company
I hadn't put two-and-two together after I noticed that wireshark came
out of ethereal, but it doesn't seem to solve my problem anyhow. I
pulled down the ethereal package on a separate zlinux guest (so I didn't
have to worry about interference with whatever I'd screwed up on the
wireshark install/d
I may be all wet, but I use tcpdump to capture the "raw" trace data;
tcpdump -i eth0 -w eth0.trc
Then use etereal gui to look/filer it.
Thanks
-
Please consider the environment before printing this email and any
attachments.
This e-mail and any attachments
I just got Debian install under VM and upon the first boot, after
installation, I'm getting:
/dev/dasdd1: clean, 15/150480 files, 26742/600816 blocks
boot: clean, 19/31264 files, 4961/31248 blocks
/dev/dasda1 is mounted. e2fsck: Cannot continue, aborting.
On Fri, April 9, 2010 01:31, Romanowski, John (OFT) wrote:
> I used the "add the new PVs and delete the old (and let LVM migrate the
> extents)" method to move off dasd and it worked well. If you can't take
> the filesystems down the method has the advantage of no downtime, and LVM
> moves only the
