Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

When I add a LUN (100GB), i non correct to map on system. The system displays 16T.

The LUN has been detached, the server has been rebooted, and I already deleted 3600a0b80006e6a66000040a95066a18b-part5 from the system.

OS: SUSE 10 sp4
SAN: DS5300

C01-OraDB-01:/dev/mapper # df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/system-rootlv
                      276G   11G  265G   4% /
udev                   16G  184K   16G   1% /dev
/dev/mapper/3600a0b80006e6a66000040a95066a18b-part5
                       16T   16T     0 100% /oradata

How do I unmount /dev/mapper/3600a0b80006e6a66000040a95066a18b-part5?

C01-OraDB-01:/dev/mapper # multipath -l
oradata (3600a0b80006e6a66000040a95066a18b) dm-2 IBM,1818      FAStT
[size=100G][features=0][hwhandler=0]
\_ round-robin 0 [prio=0][enabled]
 \_ 1:0:1:0 sdd 8:48  [failed][undef]
\_ round-robin 0 [prio=0][active]
 \_ 1:0:0:0 sdc 8:32  [active][undef]
share|improve this question
    
I presume that a simple unmount /oradata/ doesn't work, after all processes using the file system have been stopped? Could you show us how that fails? –  MadHatter Nov 22 '12 at 9:02
    
C01-OraDB-01:/dev/mapper # umount /oradata umount: /oradata: device is busy umount: /oradata: device is busy C01-OraDB-01:/dev/mapper # fuser /oradata /oradata: 9518c 13401 13726 13801 –  ostapv Nov 22 '12 at 9:08
    
C01-OraDB-01:/dev/mapper # ps -eaf | grep 9518 root 9518 1 0 Nov21 ? 00:00:00 /bin/ls -A -N --color=tty -T 0 -l root 19165 15152 0 11:09 pts/16 00:00:00 grep 9518 After that I kill -9 9518 but problem is still –  ostapv Nov 22 '12 at 9:10
    
Can you not reboot single-user? That should clear the mount point for sure. –  MadHatter Nov 22 '12 at 10:25

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.