11-04-2014
Ok,
Have you tried varyoffvg patchtest?
If that doesn't varyoff, then you have to look into each vhost and their backing device and compare it with lsvg -l `lsvg` output.
If you see some devices from patchtest VG remove them.
This User Gave Thanks to ibmtech For This Post:
9 More Discussions You Might Find Interesting
1. Linux
Hi all,
My disk space is 100% full.
df -k <dir> -> 100%
One of my debug files consume huge amount of space and i want to remove the same to start off fresh debugs.
However i'm unable to remove the file giving out the following error message:
rm -f debug.out22621
rm: cannot remove... (8 Replies)
Discussion started by: Pankajakshan
8 Replies
2. AIX
Hello guys,
It would be so nice of you if someone can provide me with these informations.
1) My SAN group assigned 51G of LUN space to the VIO server.I ran cfgdev to discover the newly added LUN. Unfortunately most of the disks that are in VIO server is 51G. How would I know which is the newly... (3 Replies)
Discussion started by: solaix14
3 Replies
3. Solaris
Hi Gurus,
I have to back the /var to other disk, however I am unable to do so. What I did is
Created a partition on another disk, placed file system on the slice and mounted on /mnt .
Issued following command
#ufsdump 0cfu /mnt /var
And I am getting... (2 Replies)
Discussion started by: kumarmani
2 Replies
4. Ubuntu
I am running Ubuntu Server, I recently added a new hard drive to the machine
When I run fdisk -l I see both drives.
The recently added drive is present but it's listed as extended.
when I try to mount the drive it says you must specify the file system type.
I can't mount this drive, I was... (2 Replies)
Discussion started by: NelsonC
2 Replies
5. AIX
Hello,
Lets say for simplicity that I do not use any vlan config inside my server - one lpar group use hea physical port1, another group hea physical port2. Physical port1 configured as vlan1 on external switch, physical port2 as vlan2.
What is the common practice - should I isolate my vios... (0 Replies)
Discussion started by: vilius
0 Replies
6. AIX
is there any way to create shared virtual disk between two LPARs like how you can do it using Storage through Fiber on two servers ?
Trying to stimulate HACMP between two LPARs (1 Reply)
Discussion started by: filosophizer
1 Replies
7. Solaris
Update:
The / file system (/dev/rdsk/c1t0d0s0) is being checked
fsck unable to stat
WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F ufs /dev/rdsk/c1t0d0s0).
Root password for system maintenance (control-d to bypass):
I am unable to hit control-d to by pass.
I... (50 Replies)
Discussion started by: br1an
50 Replies
8. AIX
Hello,
VIOS 2.2.1.4 using IVM.
I'm trying to extend a virtual disk assigned to a running lpar so that I can expand the lpar's datavg and grow some filesystems for the user.
Storage admin expanded the lun and new size was reflected in VIO right away. I then needed the storage pool to... (2 Replies)
Discussion started by: j_aix
2 Replies
9. UNIX for Advanced & Expert Users
Hi everybody,
I have Power5 server with 4 internal hdisks each of 70Gb.
VIOS server was installed via Virtual I/O Server Image Repository on the HMC.
HMC release - 7.7.0
VIOS rootvg installed on 2 disk(these disks merged to one storage pool during VIOS install process),and 2 others hdisks... (2 Replies)
Discussion started by: Ravil Khalilov
2 Replies
LEARN ABOUT DEBIAN
th-cmd
TH-CMD(1) Triggerhappy daemon TH-CMD(1)
NAME
th-cmd -- triggerhappy commander
SYNOPSIS
th-cmd --socket <socket> [--passfd] [--tag <foo>] [--clear|--enable|--disable|--mode <mode>|--quit|--udev|--add <devices...>|--remove
<devices...>]
DESCRIPTION
This program is used to issue commands to a running triggerhappy daemon. It utilizes an unix domain socket bound by the daemon.
OPTIONS
--socket socket
The socket file opened by the running triggerhappy daemon instance.
--add <devices...>
Instruct the running daemon to open the input devices specified on the command line
--remove <devices...>
Remove specified devices from the running daemon.
--clear
Remove all devices from the running daemon.
--udev
Deduce operation and device name from udev environment (for use in udev rules).
--disable
Disable the execution of triggers.
--enable
Re-enable the execution of triggers.
--mode <newmode>
Change the mode of the triggerhappy daemon to <newmode>. If no new mode is specified, the daemon switches to default mode.
--quit
Terminate the triggerhappy daemon.
--passfd
Instead of instructing the daemon to open the device, open the device and pass the file descriptor to the daemon. This allows the
adding of new devices to a daemon having dropped its privileges, however the th-cmd process must have access to the device file.
--grab
Grab the device; the triggerhappy daemon will try to get exclusive access to the device, other applications will not receive the events
emitted by it.
--tag foo
Label the added device with the tag <foo>; this can be used to limit the scope of event handlers to a subset of input devices.
AUTHOR
Stefan Tomanek <stefan.tomanek+th@wertarbyte.de>
0.3.4 2011-05-10 TH-CMD(1)