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 V7
icheck
ICHECK(1M)ICHECK(1M)NAME
icheck - file system storage consistency check
SYNOPSIS
icheck [ -s ] [ -b numbers ] [ filesystem ]
DESCRIPTION
Icheck examines a file system, builds a bit map of used blocks, and compares this bit map against the free list maintained on the file sys-
tem. If the file system is not specified, a set of default file systems is checked. The normal output of icheck includes a report of
The total number of files and the numbers of regular, directory, block special and character special files.
The total number of blocks in use and the numbers of single-, double-, and triple-indirect blocks and directory blocks.
The number of free blocks.
The number of blocks missing; i.e. not in any file nor in the free list.
The -s option causes icheck to ignore the actual free list and reconstruct a new one by rewriting the super-block of the file system. The
file system should be dismounted while this is done; if this is not possible (for example if the root file system has to be salvaged) care
should be taken that the system is quiescent and that it is rebooted immediately afterwards so that the old, bad in-core copy of the super-
block will not continue to be used. Notice also that the words in the super-block which indicate the size of the free list and of the i-
list are believed. If the super-block has been curdled these words will have to be patched. The -s option causes the normal output
reports to be suppressed.
Following the -b option is a list of block numbers; whenever any of the named blocks turns up in a file, a diagnostic is produced.
Icheck is faster if the raw version of the special file is used, since it reads the i-list many blocks at a time.
FILES
Default file systems vary with installation.
SEE ALSO dcheck(1), ncheck(1), filsys(5), clri(1)DIAGNOSTICS
For duplicate blocks and bad blocks (which lie outside the file system) icheck announces the difficulty, the i-number, and the kind of
block involved. If a read error is encountered, the block number of the bad block is printed and icheck considers it to contain 0. `Bad
freeblock' means that a block number outside the available space was encountered in the free list. `n dups in free' means that n blocks
were found in the free list which duplicate blocks either in some file or in the earlier part of the free list.
BUGS
Since icheck is inherently two-pass in nature, extraneous diagnostics may be produced if applied to active file systems.
It believes even preposterous super-blocks and consequently can get core images.
ICHECK(1M)