06-11-2014
I never had stale on HP-UX... (cant say that of the aix's I was in charge...) So I am trying to interpolate from my bad AIX experience... About Contiguous - You do have some... HP-UX11.11 have in vg00 3 Lvols that use contiguous: the swap, root and stand, but its not the case here, how did you change disk? (what commands were passed...) because I think I did have something of the sort with a D class when I forgot to do a ??? forgot.. trying hard to remember you can help since I have no more documentation, you should do a ioscan ( full in doubt, not funC...) to update devs but there is something else I wonder if its not insf -e can you check what that does? because my idea would be to remove the disk if you are sure it is good with no bad blocks etc.. the rm all associated files /dev/rdsk/c.... then add the disk do an insf if its the right command and see if that changes after mirroring again
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi, I get an error saying "Stale NFS file handle"
how can I solve this? Is it possible to do this with a umount/ mount command? (5 Replies)
Discussion started by: rein
5 Replies
2. UNIX for Dummies Questions & Answers
Is there an easy way to find all stale mounts on a system? (2 Replies)
Discussion started by: derf912
2 Replies
3. UNIX for Dummies Questions & Answers
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)
Discussion started by: karthikosu
2 Replies
4. HP-UX
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)
Discussion started by: rajeshtt32
1 Replies
5. UNIX and Linux Applications
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)
Discussion started by: alphasahoo
3 Replies
6. AIX
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)
Discussion started by: navadeep
6 Replies
7. HP-UX
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)
Discussion started by: LisaS
8 Replies
8. Solaris
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)
Discussion started by: poyato
2 Replies
9. AIX
Hi friends,
the paging lv hd6 is in stale condition
hd6 paging 48 96 2 open/stale N/A
And i'am getting the following alerts in the server 333BD283 0811044814 U S LVDD Bad block detected with no relocation al
333BD283 0811041114 U S LVDD ... (1 Reply)
Discussion started by: Mohamed Thamim
1 Replies
10. AIX
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 OPENDARWIN
badsect
BADSECT(8) BSD System Manager's Manual BADSECT(8)
NAME
badsect -- create files to contain bad sectors
SYNOPSIS
/etc/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 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 it will ask ``HOLD BAD BLOCK ?'' A posi-
tive response will cause fsck to convert the inode to a regular file containing the bad block.
SEE ALSO
bad144(8), fsck(8), format(8)
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.
BUGS
If more than one sector which comprise 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.
HISTORY
The badsect command appeared in 4.1BSD.
4th Berkeley Distribution June 5, 1993 4th Berkeley Distribution