I am confused as to how the disk is coming to client?
Have you created a VG on VIOS, created LV and giving those LV's as vscsi disks to client? or you have mapped the whole disk to client?
If your answer is latter then you cannot create a VG on VIOS.
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)
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)
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)
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)
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)
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)
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)
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)
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 OSF1
volreattach
volreattach(8) System Manager's Manual volreattach(8)NAME
volreattach - Reattaches disk drives that have once again become accessible
SYNOPSIS
/usr/sbin/volreattach [-rb] [accessname...]
/usr/sbin/volreattach -c accessname
OPTIONS
The volreattach utility has the following options: Calls the volrecover utility to attempt to recover stale plexes of any volumes on the
failed disk. Performs the reattach operation in the background. Checks whether a reattach is possible. No operation is performed, but the
name of the disk group and disk media name at which the disk can be reattached is displayed.
DESCRIPTION
The volreattach utility attempts to reattach disks using the same disk group and media names they had before detachment.
This operation may be necessary if a disk has a transient failure, or if some disk drivers are unloaded or unloadable when the Logical
Storage Manager is started, causing disks to enter the failed state.
If the problem is fixed, the volreattach command can be used to reattach the disks without plexes being flagged as stale, as long as the
reattach happens before any volumes on the disk are started.
The volreattach command is called from the voldiskadm menus as part of disk recovery.
The volreattach utility tries to find a disk with a disk group and disk ID matching that of the disk(s) being reattached. If the matching
disk is found, the reattach operation may still fail if the original cause (or some other cause) for the disk failure still exists.
EXIT CODES
A zero exit status is returned if it is possible to perform a reattach. Otherwise, non-zero is returned.
SEE ALSO volintro(8), voldiskadm(8), volrecover(8)volreattach(8)