Archive for July, 2008

Having trouble unmounting a file system in Unix

So you are trying to unmount a file system for some reason and it just wont let you. It keeps on telling you that it is busy. Whats the deal. You already cd to / so you are not the culprit. So instead of kicking everyone off the box just figure out who the offender is and yell at them.

Excerpt from /var/adm/messages

6 server05 mount[4691]: [ID 612810 user.error] mount: /www: Device busy
Feb 5 07:41:19 server05 mount[4708]: [ID 612810 user.error] mount: /www: Device busy
Feb 5 07:41:43 server05 mount[4717]: [ID 612810 user.error] mount: /www: Device busy
Feb 5 07:43:30 server05 mount[4949]: [ID 612810 user.error] mount: /www: Device busy
Feb 5 07:49:55 server05 mount[5273]: [ID 612810 user.error] mount: /www: Device busy
Feb 5 07:53:39 server05 mount[5656]: [ID 612810 user.error] mount: /www: Device busy
Feb 5 07:54:31 server05 mount[5713]: [ID 612810 user.error] mount: /www: Device busy

use fuser to identify the process that is causing the trouble.

server05% fuser /www
/www: 4053c

server05% ps -ef | grep 4053
abe 4061 4053 0 07:27:20 pts/3 0:00 less access
abe 4053 4031 0 07:26:50 pts/3 0:00 bash
abe 4075 4053 0 07:28:05 pts/3 0:00 less access
abe 4067 4053 0 07:27:42 pts/3 0:01 less access
abe 4122 4053 0 07:28:44 pts/3 0:00 more
abe 4121 4053 0 07:28:44 pts/3 0:00 grep -i keep-a access
louis 6983 6950 0 08:14:57 pts/1 0:00 grep 4053

Comments

Set terminal to VT100 and Editor to VI

So you go to use crontab -e and you get some strange stuff at the bottom of the line.  Yup you are in ee, which is even older then vi.  This can often happen when you are using a serial connection, and even when using ssh.  This is a simple fix, with examples below.

TERM=vt100 ; export TERM ; EDITOR=vi;export EDITOR

user@server:~$ echo $TERM
xterm
user@server:~$ TERM=vt100 ; export TERM ; EDITOR=vi;export EDITOR
user@server:~$ echo $TERM
vt100

Comments

How to change the dump directory on a soalris server

HOW TO CHANGE THE DUMP DIRECOTRY

# dumpadm -d /dev/dsk/c0t0d0s1
Dump content: kernel pages
Dump device: /dev/dsk/c0t0d0s1 (dedicated)
Savecore directory: /var/crash/unknown
Savecore enabled: no
# dumpadm -y
Dump content: kernel pages
Dump device: /dev/dsk/c0t0d0s1 (dedicated)
Savecore directory: /var/crash/unknown
Savecore enabled: yes

Comments

« Previous Page« Previous entries « Previous Page · Next Page » Next entries »Next Page »