01-22-2012
On second thought - try the canned whoio.d script, it prints more like what you need.
Assuming the problem is a single process or a bunch of process LWP's.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I try add a new file system:
#zfs create dsk1/mqm
it came back with:
#cannot create 'dsk1/mqm': no such pool 'dsk1'
what do I have to do?
Kind regards
Mehrdad (2 Replies)
Discussion started by: mehrdad68
2 Replies
2. Solaris
Is it possible to use zvol from SAN LUN to install LDOM OS ? I 'm using following VDS from my service domain
VDS
NAME LDOM VOLUME DEVICE
primary-vds0 primary iso sol-10-u6-ga1-sparc-dvd.iso
cdrom ... (16 Replies)
Discussion started by: fugitive
16 Replies
3. Shell Programming and Scripting
I am working on a server where the 'root' user ZFS filesystem.
Now when I do Top commands it says only 750M free .But when I count the actual memory utilized it comes only to 12 GB and the total size of the server is 32G.
I think rest of the space is held up by ZFS file system.
Is there a... (5 Replies)
Discussion started by: prasperl
5 Replies
4. Solaris
Hi All,
I am using this commands to dynamically increase ZFS swap space on Solaris
my question is:
1- after i make these commands it will permanent or it will remove after restart
2- how to make it permanent
# swap -l
swapfile dev swaplo bloques libre
/dev/zvol/dsk/rpool/swap... (4 Replies)
Discussion started by: osmanux
4 Replies
5. Solaris
Hi,
I have Solaris-10 (Update-7). This is having ZFS file-system and 10 sparse-root zones are there. I want to install Solaris-10 recommended patch cluster on it, but not sure, how to go ahead with procedure. I want to patch one side of the mirror and keep intact another side safe in case of... (6 Replies)
Discussion started by: solaris_1977
6 Replies
6. Emergency UNIX and Linux Support
Hi All,
I have Solaris-10 configured with two non-global zones. All file-systems are mounted on global zone and data file-systems are mounted on non-global zone as lofs.
I have added 4 luns of 100 GB each and still not able to extend a file-system. This is production server, so I can not... (5 Replies)
Discussion started by: solaris_1977
5 Replies
7. Solaris
Hi,
I have a machine, and mpzio fails everytime i reboot the server. The machine has tape drives and SAN storage, I'm not sure if that is my issue or not. I was told to not enable mpxio globally as that would do something bad to the tape drives. So, I set it to only make the two SAN connected... (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
8. Solaris
I have Solaris-10 server running ZFS file-system. ctdp04_vs03-pttmsp01 is one of the non global zone. I wanted to increase a /ttms/prod file-system of zone, which is actually /zone/ctdp04_vs03-pttmsp01/ttms/prod on global server.
I have added a new disk of 9 GB, which is emcpower56a and now I can... (16 Replies)
Discussion started by: solaris_1977
16 Replies
9. Solaris
Hi all,
I'm using Solaris 11.3.
HBA port connected to SAN disk 3T.
AVAILABLE DISK SELECTIONS:
0. c0t600A0B800033696A0000214B571938F1d0 <SUN-CSM200_R-0760 cyl 44556 alt 2 hd 255 sec 189>
/scsi_vhci/ssd@g600a0b800033696a0000214b571938f1
1. c2t3C58620E0C565100d0... (1 Reply)
Discussion started by: manhte1
1 Replies
10. Solaris
Hi
I have the following file system, that needs to be expanded to more 500Gb, so a total of 1Tb:
df -h /oradata1
Filesystem Size Used Available Capacity Mounted on
oradata1 587G 517G 69G 89% /oradata1
I am not familiar with zfs, I am more... (17 Replies)
Discussion started by: fretagi
17 Replies
LEARN ABOUT OPENSOLARIS
ps_lcontinue
ps_pstop(3PROC) Process Control Library Functions ps_pstop(3PROC)
NAME
ps_pstop, ps_pcontinue, ps_lstop, ps_lcontinue, ps_lrolltoaddr, ps_kill - process and LWP control in libthread_db
SYNOPSIS
#include <proc_service.h>
ps_err_e ps_pstop(struct ps_prochandle *ph);
ps_err_e ps_pcontinue(struct ps_prochandle *ph);
ps_err_e ps_lstop(struct ps_prochandle *ph, lwpid_t lwpid);
ps_err_e ps_lcontinue(struct ps_prochandle *ph,
lwpid_t lwpid);
ps_err_e ps_lrolltoaddr(struct ps_prochandle *ph,
lwpid_t lwpid, psaddr_t go_addr, psaddr_t stop_addr);
ps_err_e ps_kill(struct ps_prochandle *ph, int signum);
DESCRIPTION
The ps_pstop() function stops the target process identified by ph, while the ps_pcontinue() function allows it to resume.
The libthread_db() function uses ps_pstop() to freeze the target process while it is under inspection. Within the scope of any single call
from outside libthread_db to a libthread_db routine, libthread_db will call ps_pstop(), at most once. If it does, it will call ps_pcon-
tinue() within the scope of the same routine.
The controlling process may already have stopped the target process when it calls libthread_db. In that case, it is not obligated to resume
the target process when libthread_db calls ps_pcontinue(). In other words, ps_pstop() is mandatory, while ps_pcontinue() is advisory. After
ps_pstop(), the target process must be stopped; after ps_pcontinue(), the target process may be running.
The ps_lstop() and ps_lcontinue() functions stop and resume a single lightweight process (LWP) within the target process ph.
The ps_lrolltoaddr() function is used to roll an LWP forward out of a critical section when the process is stopped. It is also used to run
the libthread_db agent thread on behalf of libthread. The ps_lrolltoaddr() function is always called with the target process stopped, that
is, there has been a preceding call to ps_pstop(). The specified LWP must be continued at the address go_addr, or at its current address if
go_addr is NULL. It should then be stopped when its execution reaches stop_addr. This routine does not return until the LWP has stopped at
stop_addr.
The ps_kill() function directs the signal signum to the target process for which the handle is ph. It has the same semantics as kill(2).
RETURN VALUES
PS_OK The call completed successfully. In the case of ps_pstop(), the target process is stopped.
PS_BADLID For ps_lstop(), ps_lcontinue() and ps_lrolltoaddr(); there is no LWP with id lwipd in the target process.
PS_ERR The function did not return successfully.
ATTRIBUTES
See attributes(5) for description of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|MT Level |Safe |
+-----------------------------+-----------------------------+
SEE ALSO
kill(2), libc_db(3LIB), proc_service(3PROC), attributes(5), threads(5)
SunOS 5.11 22 Mar 2001 ps_pstop(3PROC)