error with SAM running "disk and file system"

[James Ellis_1]

Yesterday I went into SAM and ran the "disk and file system" icon. It took forever and nothing came up, so I tried to get out of this and could not close the window. I believe this is related to the command I ran this causing my ioscan not to run this morning. I was checking what the device_file was for the DVD CDROM.

Anyway, when I do a ps -ef I still show SAM as running and cannot kill it, it will not terminate.
I believe I did something to fix this problem before, but forgot what I did. Any help? Thanks.

[Pete Randall]

A simulated power failure will probably do the trick.

Seriously, I'm not sure what you can do if you can't kill it. Now that the search feature is functioning again, I'll go poke around and let you know if I can find anything.

Pete

[Alessio_6]

Hi,

maybe SAM is still running the command to show you the disk devices.
You should kill it, it should be something like ../samx/..

hope this help

regards,
Alessio

[Jean-Louis Phelix]

hi,

ioscan hang could also unfortunately mean that you have a disk problem ... Nothing in dmesg or syslog.log ?

Regards.

[James Ellis_1]

Alesso,
Yes. When I do a ps-ef | grep sam the results that come up show something like /samx/...and I cannot kill this. I think it is still running....I will check if there is a disk problem, which I doubt because we just completed a demo. Let me check...thanks.

[John Bolene]

sounds like SAM is waiting on an I/O that will never complete, this makes a zombie like process

I would suspect that an I/O device is about to go really bad

[S.K. Chan]

SAM is notoriously inconsistent with its report (if not patched correctly), I've always try to avoid using SAM as much as I could. In your case I think if it can't be killed, eventually it should time out. Check the SAM log and see what it says (/var/sam/log/samlog) and if you look closely, sam should have 2 to 3 child processes in the process list. Look for it's parent process and kill that one. Last resort (may worth a try) is to remove the lock file in /var/sam/lock and then try to kill it.

[James Ellis_1]

Hi S.K,
I looked in the /sam/samlog and it shows the last thing as a Memory Fault (core dump). Also I did not see anything like child process.

Since you mentioned lock in your message, I went to the /var/sam/lock and saw that the date of this lick was the exact time I started this yesterday...and there is "0" data in this lock file. Do I just delete this file (lock_2) and then kill the /samx/ PID in ps -ef?
Thanks!

[S.K. Chan]

When you run ..
# ps -ef|grep sam
you should at least see 2 processes ..
- samx
- /usr/sbin/sam
Isn't that the case for you ? Usually killing the 2nd process (ie /usr/sbin/sam) would kill all of 'em. The parent process for /usr/sbin/sam would be "-sh" (the shell) that launched it. Have you try killing that shell ? The /var/sam/lock dir would have a zero size file typically named "lock_ttyXX" which prevent multiple session of SAM running at the same time. Come to think of it, it's NOT a good idea to delete that file then try killing SAM, because if SAM is not "killable" then someone else might be able to run SAM concurrently.

[James Ellis_1]

I only see two processes:

-samx
and
/usr/bin/sh /usr/sam/lbin/ioparser.sh -f All

I believe this is the problem when I try to run ioscan...seem the ioscan cannot finish running its task.