Just for the record: "stale" means you have two (or more) mirror copies of a logical volume of which one (or more) are missing.
Now, this is most probably the cause of your problems: when a physical disk is being formatted several blocks are set aside as spare. Should one allocated disk block become unreliable for some reason (the magnetic coating becomes defective somehow), then the driver automatically marks this block as "bad" and uses one of the set aside spare blocks instead. The data from the old block are transferred to the new location if this is still possible. This is called "bad block relocation".
hd6 is your swap and swap is basically memory. You do not want to tinker with the memory while the system is running, so there is a rationale behind this. But because bad block relocation is turned off, the system in turn cannot reloctae the block and therefore you have a stale LV.
My suggestion is to remove the stale mirror from the LV and then remirror it. Once the bad block is not any more part of an LV it will simply be marked as bad and not be used again should the surrounding space be reallocated to another LV.
hi, i was trying to mirror root volume group and the command i was using didnt respond for a long time
mirrorvg -m rootvg hdisk1
I was checking rootvg and it gives below. how do i fix stale partitions?? it seems to be on hdisk1
LV NAME TYPE LPs PPs PVs LV STATE ... (2 Replies)
hi All
I have one RP 3410 server with hp-ux 11.23 mirror disk
it's lvdislay -v /dev/vg00/lvol4 shows stale in some location
Actual is current
pls help me to resolve the probem
I have check with lvsync command and vgsync
but not working
re
Rajesh (1 Reply)
There are a filesystem /GWD/appbase/projects/GRIDDB
Under this filesystem there is a directory called backup.
But When I am trying to access the backup directory ,it is showing me the following error:
# cd /GWD/appbase/projects/GRIDDB
# cd backup
-bash: cd: backup: Stale NFS file handle
... (3 Replies)
my AIX server used to have scsi disk hdisk4. Now i removed that disk. But still it is still listed in lspv. So how can i remove the stale entry of it ? (6 Replies)
HP-UX B.11.23 U ia64
I've got two users that show in "w" with long idle times but if I search for their processes I find nothing (ps -ef | grep username )
I'm not sure why "w" still sees them and if there is anything (short of a reboot) that I can do to clean them out.
Ideas? (8 Replies)
Any package that I try to install, is giving an error of 'lock':
# pkgadd -d openssl-1.0.0g-sol10-sparc-local
The following packages are available:
1 SMCossl openssl
(sparc) 1.0.0g
Select package(s) you wish to process (or 'all' to process
all packages).... (2 Replies)
Hello,
I have an ancient HP-UX 11.11 system where I have a logical volume marked stale and I can't get it sync'd. I have tried lvsync and lvreduce/lvextend to no avail. It is just one 4Mb PE on the disk that I can't get current.
# lvdisplay -v /dev/vg00/lvol5 | grep stale
LV Status ... (17 Replies)
Hi everybody,
I have a little problem with my AIX 6.1, PowerHA 6.1 LVM mirror. After problem with SAN pathing of our one Datacenter, I have LV at stale state.
# lsvg cpsdata2vg
VOLUME GROUP: cpsdata2vg VG IDENTIFIER: 00fb518c00004c0000000169445f4c2c
VG STATE: ... (6 Replies)
Discussion started by: Necronomic
6 Replies
LEARN ABOUT HPUX
lssf
lssf(1M)lssf(1M)NAME
lssf - list a special file
SYNOPSIS
special_file ...
special_file
DESCRIPTION
In the first form, lists information about a special file. For each special_file name, determines the major number of the special file and
whether it is block or character (using It then scans the system for the device that is associated with the special file. When the device
is found, the minor number of the special file is decoded.
A mnemonic description of the minor number is printed on standard output along with the hardware path (in other words, address) of the
device. Mnemonics used to describe the fields are closely related to the options used with (see mksf(1M)).
In the second form, displays the list of stale device special files present in selected directories under the directory.
In the third form, executes a Critical Resource Analysis (CRA) on the
Options
recognizes the following options:
Displays the Critical Resource Analysis (CRA) of
Displays the stale device special files present in the
directories below, which contain special files for mass storage devices. The stale device special files correspond to nodes
that have an entry in the system I/O configuration files but the corresponding device is not found. The device special files
can either be legacy or persistent (see intro(7)).
DIAGNOSTICS
Most diagnostic messages from are self explanatory. Listed below are some messages deserving further clarification. Warnings allow to
continue.
Warnings
There is no information about the device in the kernel.
The special file is not usable. Use to remove the special file (see rmsf(1M)).
The major number associated with the special file is not in the kernel.
Use to add the appropriate driver to the kernel (see kcmodule(1M)).
The indicated device driver or device class
is not present in the kernel. An of a special file pointing to an unusable device fails. To make the device usable, the appro-
priate device driver and/or device class must be added to the kernel using If the device is no longer needed, should be used to
remove the special files and update the system I/O configuration files.
The file is not associated with an IO device.
EXAMPLES
Suppose a special file is created with the command The command then produces:
Suppose a special file is created with the command The command then produces:
Display stale device special files:
Display Critical Resource Analysis information for /dev/disk/disk7:
AUTHOR
was developed by HP.
FILES
I/O system special file
I/O system configuration database
I/O system configuration database
SEE ALSO insf(1M), kcmodule(1M), mksf(1M), rmsf(1M), intro(7).
lssf(1M)