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 CENTOS
pmgetarchiveend
PMGETARCHIVEEND(3) Library Functions Manual PMGETARCHIVEEND(3)NAME
pmGetArchiveEnd - locate logical end of file for an archive log
C SYNOPSIS
#include <pcp/pmapi.h>
int pmGetArchiveEnd(struct timeval *tvp);
cc ... -lpcp
DESCRIPTION
Assuming the current PMAPI context is associated with an archive log, pmGetArchiveEnd will attempt to find the logical end of file (after
the last complete record in the archive), and return the last recorded timestamp via tvp. This timestamp may be passed to pmSetMode(3) to
reliably position the context at the last valid log record, e.g. in preparation for subsequent reading in reverse chronological order.
For archive logs that are not concurrently being written, the physical end of file and the logical end of file are co-incident. However if
an archive log is being written by pmlogger(1) at the same time an application is trying to read the archive, the logical end of file may
be before the physical end of file due to write buffering that is not aligned with the logical record boundaries.
pmGetArchiveEnd returns an error less than zero if the context is neither valid, nor associated with an archive, or the archive is seri-
ously corrupted. Otherwise, the return value is 0 if there has been no change of state since the last call, or 1 if the logical end of
file has advanced since the last call.
In the absence of an error, the result returned via tvp is well-defined.
pmGetArchiveEnd preserves the positioning state of the log file prior to this function call.
PCP ENVIRONMENT
Environment variables with the prefix PCP_ are used to parameterize the file and directory names used by PCP. On each installation, the
file /etc/pcp.conf contains the local values for these variables. The $PCP_CONF variable may be used to specify an alternative configura-
tion file, as described in pcp.conf(5). Values for these variables may be obtained programmatically using the pmGetConfig(3) function.
SEE ALSO PMAPI(3), pmFetch(3), pmFetchArchive(3), pmGetArchiveLabel(3), pmGetConfig(3), pmSetMode(3), pcp.conf(5) and pcp.env(5).
DIAGNOSTICS
PM_ERR_NOCONTEXT
the current PMAPI context is either invalid, or not associated with an archive log
PM_ERR_LOGREC
the archive is sufficiently damaged, that not a single valid record can be found
Performance Co-Pilot PCP PMGETARCHIVEEND(3)