Adding a second disk to increase the space for /var on first dislk : but umount /var failed

[Tobias Hoellrich]

> -----Original Message-----
> From: owner-freebsd-questions at freebsd.org 
> [mailto:owner-freebsd-questions at freebsd.org] On Behalf Of dhaneshk k
> Sent: Tuesday, June 10, 2008 7:15 AM
> To: questions at freebsd.org
> Cc: Manolis Kiagias
> Subject: Adding a second disk to increase the space for /var 
> on first dislk : but umount /var failed
> 
> I am able to   umount  /mnt                       but not   /var 
> 
> [root at storm ~]# umount /var/
> umount: unmount of /var failed: Device busy
> [root at storm ~]# umount /mnt/
> [root at storm ~]# umount /var/
> umount: unmount of /var failed: Device busy
> [root at storm ~]# df -h
> Filesystem     Size    Used   Avail Capacity  Mounted on
> /dev/ad7s1a    496M    329M    127M    72%    /
> devfs          1.0K    1.0K      0B   100%    /dev
> /dev/ad7s1e    496M    5.4M    451M     1%    /tmp
> /dev/ad7s1f     44G     38G    2.9G    93%    /usr
> /dev/ad7s1d    1.4G    221M    1.1G    16%    /var
> devfs          1.0K    1.0K      0B   100%    /var/named/dev
> [root at storm ~]# umount /dev/ad7s1
> ad7s1   ad7s1a  ad7s1b  ad7s1c  ad7s1d  ad7s1e  ad7s1f  
> [root at storm ~]# umount /dev/ad7s1d 
> umount: unmount of /var failed: Device busy
> [root at storm ~]# umouny /var/ 
> bash: umouny: command not found
> [root at storm ~]# umouny /var 
> bash: umouny: command not found
> [root at storm ~]# umount /var
> umount: unmount of /var failed: Device busy
> [root at storm ~]# pwd
> /root
> [root at storm ~]# umount /var
> umount: unmount of /var failed: Device busy
> [root at storm ~]# 
> 
> 
> 
> getting an error   Error 
> org.freedesktop.Hal.Device.PermissionDeniedByPolicy.
> 
> Details  hal-storage-fixed -mount    refused uid 0       How 
> to fix this and umount /var
>  
> 
> Any hints most welcome : 


Did you switch to single user-mode (shutdown now) before trying to
umount /var? If you did, there may be some other process still using
files/dirs in "/var". If you have lsof installed
(/usr/ports/sysutils/lsof), you can identify (as root) which process
still using stuff in /var:

santafe# lsof +D /var/
COMMAND    PID  USER   FD   TYPE     DEVICE SIZE/OFF     NODE NAME
dhclient   321 _dhcp  cwd   VDIR      0,100      512 14578696 /var/empty
dhclient   321 _dhcp  rtd   VDIR      0,100      512 14578696 /var/empty
dhclient   321 _dhcp  jld   VDIR      0,100      512 14578696 /var/empty
dhclient   321 _dhcp    6w  VREG      0,100     1007 14582324
/var/db/dhclient.leases.msk0
devd       537  root    4u  unix 0xc6a78188      0t0
/var/run/devd.pipe
devd       537  root    5w  VREG      0,100        3 14580313
/var/run/devd.pid
syslogd    603  root    3w  VREG      0,100        3 14580315
/var/run/syslog.pid
syslogd    603  root    4u  unix 0xc6a84310      0t0
/var/run/log
syslogd    603  root    5u  unix 0xc6a84188      0t0
/var/run/logpriv
...

Stop the processes (dhclient, devd, syslogd, etc.) that still use /var
and then try to umount it again.

Hope this helps - Tobias