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 NETBSD
badsect
BADSECT(8) BSD System Manager's Manual BADSECT(8)NAME
badsect -- create files to contain bad sectors
SYNOPSIS
badsect bbdir sector ...
DESCRIPTION
badsect makes a file to contain a bad sector. Normally, bad sectors are made inaccessible by the standard formatter, which provides a for-
warding table for bad sectors to the driver; see bad144(8) for details. If a driver supports the bad blocking standard it is much preferable
to use that method to isolate bad blocks, since the bad block forwarding makes the pack appear perfect, and such packs can then be copied
with dd(1). The technique used by this program is also less general than bad block forwarding, as badsect can't make amends for bad blocks
in the i-list of file systems or in swap areas.
On some disks, adding a sector which is suddenly bad to the bad sector table currently requires the running of the standard DEC formatter.
Thus to deal with a newly bad block or on disks where the drivers do not support the bad-blocking standard badsect may be used to good
effect.
badsect is used on a quiet file system in the following way: First mount the file system, and change to its root directory. Make a directory
BAD there. Run badsect giving as argument the BAD directory followed by all the bad sectors you wish to add. The sector numbers must be
relative to the beginning of the file system, but this is not hard as the system reports relative sector numbers in its console error mes-
sages. Then change back to the root directory, unmount the file system and run fsck(8) on the file system. The bad sectors should show up
in two files or in the bad sector files and the free list. Have fsck(8) remove files containing the offending bad sectors, but do not have
it remove the BAD/nnnnn files. This will leave the bad sectors in only the BAD files.
badsect works by giving the specified sector numbers in a mknod(2) system call, creating an illegal file whose first block address is the
block containing bad sector and whose name is the bad sector number. When it is discovered by fsck(8) it will ask ``HOLD BAD BLOCK ?'' A
positive response will cause fsck(8) to convert the inode to a regular file containing the bad block.
DIAGNOSTICS
badsect refuses to attach a block that resides in a critical area or is out of range of the file system. A warning is issued if the block is
already in use.
SEE ALSO bad144(8), fsck(8)HISTORY
The badsect command appeared in 4.1BSD.
BUGS
If more than one of the sectors in a file system fragment are bad, you should specify only one of them to badsect, as the blocks in the bad
sector files actually cover all the sectors in a file system fragment.
BSD June 5, 1993 BSD