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 DEBIAN
lockmail.maildrop
LOCKMAIL(1) Double Precision, Inc. LOCKMAIL(1)NAME
lockmail - create mail lock files
SYNOPSIS
lockmail [-r] [-t timeout] {lockfile} {program} [argument...]
DESCRIPTION
lockmail is a helper utility for working with mailbox files. Mailbox files must be locked to prevent other applications from modifying the
mailbox at the same time. Different system use different locking conventions. lockmail uses two of the most common locking mechanisms in
use, which should work reliably on most systems.
lockfile is the pathname to an existing mailbox file. By default, lockmail tries to lock the mailbox every five seconds (if the mailbox is
already locked), and will give up after three minutes. After the mailbox is successfully locked, lockmail runs program as a child process,
with any optional arguments. When program terminates, lockmail removes the mailbox lock, and terminates itself.
OPTIONS -r
If a regular lock fails, try a read-only lock. Use this option to lock mailbox files in a read-only directory.
-t timeout
If the lock attempt fails, try again for up to timeout seconds. The actual timeout is rounded up to the next five second interval (a
lock attempt is tried every five seconds).
DESCRIPTION
This section briefly describes the locking mechanism used by lockmail. lockmail uses three different locking conventions in order to
maximize compatibility with other mail software: C-Client folder locks, dot-locks, and file locks.
C-Client folder locks
Mail software based on the C-Client library creates lock files named /tmp/.dddddd.iiiiii. Here, dddddd and iiiiii are the device number and
the inode number of the mailbox file (the st_dev and st_ino fields in the inode), in hexadecimal. If the process ID saved in the C-Client
folder lock file is not valid, lockmail concludes that it's a stale lock file, and will remove it.
Note
A race condition exists where a C-Client process is killed after it creates a lock file, but before saving its process ID in the lock
file. The race window is very small, but it exists. The C-Client library does not appear to ever clear out the lock file.
lockmail attempts to resolve this race condition by deleting zero-length lock files that are at least five minutes old.
dot-locks
lockmail also creates, and honors dot-lock files. Dot-lock files are first created as temporary files, then linked to lockfile.lock. The
link operation fails if the dot-lock file already exists. lockmail uses an enhanced method of dot-locking, where its process ID, and the
name of the server where lockmail is running is also saved in its dot-lock file. If the operation fails due to an existing dot-lock file
that was created by another lockmail process on the same server, and the process ID no longer exists, this stale dot-lock file is removed
immediately. In all other situations a dot-lock file older than five minutes is considered stale, and removed.
Note
A failure to create a dot-lock file is silently ignored if the reason for the failure is because lockmail does not have the write
permission in the dot-lock file's directory. The incoming mail spool directory (usually /var/mail) typically does not have global write
permissions, so the attempt to create the dot-lock file in the spool directory will fail, and lockmail will be content with using
file-locking only.
File locks
The final locking mechanism lockmail uses is the operating system's file locking facility. If lockmail fails to obtain all three locks,
lockmail will sleep for five seconds and try again. The only exception is a failure to create a dot-lock because of no write access to the
dot-lock file's directory, which is ignored. If lockmail still fails to obtain all required locks in the amount of time specified by the -t
option (or its default value), lockmail will terminate with the EX_TEMPFAIL exit code.
lockmail runs program after obtaining the last file lock, waits until program terminates, and releases all locks. program must terminate
before any of the locks obtained by lockmail expire, and are considered stale. lockmail will then terminate with the same exit code as
program.
EXIT STATUS
lockmail terminates with the same exit status as program lockmail terminates with the EX_TEMPFAIL exit status if it was unable to obtain a
lock, or if program was killed by a signal.
SEE ALSO maildrop(1)[1], sendmail(8).
AUTHOR
Sam Varshavchik
Author
NOTES
1. maildrop(1)
[set $man.base.url.for.relative.links]/maildrop.html
Courier Mail Server 08/30/2011 LOCKMAIL(1)