06-15-2015
The lsof output just means it found something (a process, file, etc) in use by a user with the UID of 1002 but that user is not listed in the /etc/passwd file. I've seen this happen two different ways, there may be more. 1) The user started some processes and was removed from the system, but the processes continue to run. 2) The user is an NIS user and something has gone horribly wrong with NIS (but I think I have maybe only seen this once).
Let's back up a bit. Can you provide more info about the circumstances leading up to the LUN being removed? For example, are you scraping an Oracle instance that was running on the system and removed the LUNs and User ID? What SAN are you using?
If there is some event matching this type of scenario then I would be confident UID 1002 still has some processes running that are using that LUN.
In that case you can run 'ps -u 1002' or 'ps -U 1002' and see if you can identify the process or processes. You can then try to stop them gracefully, kill -HUP them, or kill -9 them.
If you have some other scenario where UID 1002 may not have anything to do with the issue, please give some details and we can try to tackle it a different way.
8 More Discussions You Might Find Interesting
1. Solaris
I just installed IBMsdd on Solaris diver along with the patches recommended. I also installed 2 - 2Gigs qlogic fiber cards & the corresponding pkges for the cards.
What command can I use to scan this LUN disks from my Soalris servers. Solaris doen't seem to be seeing this disks presented on it.... (2 Replies)
Discussion started by: Remi
2 Replies
2. Solaris
Is there a limit to the number of LUNS that can be concatenated using Solaris Volume manager with Soft partitions?
I have worked with some AIX admins in the past and there was such a limitation therefore limiting the size the filesystem could grow to.
Is there such a limitation in Solaris 9... (6 Replies)
Discussion started by: BG_JrAdmin
6 Replies
3. Solaris
hi,
what are the steps to detect and configure a new attached lun in Solaris 10.
Is there any difference between cfgadm and luxadm command ?
rgds,
snjksh (5 Replies)
Discussion started by: snjksh
5 Replies
4. Solaris
How to get LUN WWN (i.e LUN mapped from a storage box say Symmetrix or clariion) in Solaris. fcinfo command does give the Target port wwn but what i'm looking for is the LUN WWN. Any help is appreciated. (2 Replies)
Discussion started by: Manish00712
2 Replies
5. Solaris
Hello to all,
Actually, currently on my Solaris box, I've a LUN (5TB space) from a EMC storage which is working fine, and a partition with ZFS filesystem is created for that LUN. as further you'll see in the logs, the "c4t6006016053802E00E6A9196B6506E211d0s2" is the current configured LUN in the... (4 Replies)
Discussion started by: Anti_Evil
4 Replies
6. Solaris
Hi,
I've noticed that mpathadm states that one of our luns has no active paths:
/dev/rdsk/c6t60000970000298700009533031324333d0s2
Total Path Count: 4
Operational Path Count: 4
/dev/rdsk/c6t60000970000298700009533031333037d0s2
... (3 Replies)
Discussion started by: badoshi
3 Replies
7. Solaris
Hi all, I have the following LUN which is showing OK with its two paths:
DEVICE PROPERTIES for disk: /dev/rdsk/c23t500507630A3BC579d123s2
Vendor: IBM
Product ID: 2107900
Revision: 3010
Serial Num: 75WB0114900
Unformatted capacity:... (13 Replies)
Discussion started by: ludiegu
13 Replies
8. Post Here to Contact Site Administrators and Moderators
ssssssssssss (0 Replies)
Discussion started by: sampathenjoy
0 Replies
PS(1) General Commands Manual PS(1)
NAME
ps, psu - process status
SYNOPSIS
ps
psu [ user ]
DESCRIPTION
Ps prints information about processes. Psu prints only information about processes started by user (default $user).
For each process reported, the user, process id, user time, system time, size, state, and command name are printed. State is one of the
following:
Moribund Process has exited and is about to have its resources reclaimed.
Ready on the queue of processes ready to be run.
Scheding about to be run.
Running running.
Queueing waiting on a queue for a resource.
Wakeme waiting for I/O or some other kernel event to wake it up.
Broken dead of unnatural causes; lingering so that it can be examined.
Stopped stopped.
Stopwait waiting for another process to stop.
Fault servicing a page fault.
Idle waiting for something to do (kernel processes only).
New being created.
Pageout paging out some other process.
Syscall performing the named system call.
no resource waiting for more of a critical resource.
FILES
/proc/*/status
SOURCE
/sys/src/cmd/ps.c
/rc/bin/psu
SEE ALSO
kill(1), db(1), ps(1), proc(3)
PS(1)