Mount issue please help

Hi all

I have a mount issue, that is as follows:

somebody as mount a certain file system

/sim5

on

/

, so when I do

df -h /sim5

it returns

Filesystem             size   used  avail capacity  Mounted on
/dev/md/dsk/d10        9.6G   7.0G   2.6G    74%    /

, which is the same as

 df -h /
Filesystem             size   used  avail capacity  Mounted on
/dev/md/dsk/d10        9.6G   7.0G   2.6G    74%    /

I try to unmount

umount /sim5

, but that did not workout

mount: warning: /sim5 not in mnttab

and if I try

mount /dev/dsk/c4t24d0s6 /sim5
mount: I/O error
mount: Cannot mount /dev/dsk/c4t24d0s6

Please can you help in this situation

How do you conclude that a file system was mounted on /sim5 ? It does not seem to follow from the commands that you posted:

You commands show,

df -h /sim5

returns
Code:

Filesystem             size   used  avail capacity  Mounted on
/dev/md/dsk/d10        9.6G   7.0G   2.6G    74%    /

So the mount is on / , not on /sim5

root@mcelvasp3 # df -h /sim5
Filesystem             size   used  avail capacity  Mounted on
/dev/md/dsk/d10        9.6G   7.0G   2.6G    74%    /
root@mcelvasp3 # df -h /
Filesystem             size   used  avail capacity  Mounted on
/dev/md/dsk/d10        9.6G   7.0G   2.6G    74%    /
root@mcelvasp3 #

They look similar to me

---------- Post updated at 11:00 AM ---------- Previous update was at 10:35 AM ----------

possible a reboot would work, but at this stage I would not like to reboot

That is a directory which resides under / (root) filesystem.

Peasant and I are saying that there does not seem to be a mount of /sim5 . The output of the commands you posted indicate that /sim5 is just a directory in the root filesystem...

Have a look at the output of lsblk .
It should print a list of partitions, and their used mountpoints.

hth

Please post the output of:

# mount

to tell us what the system thinks is mounted.

Also, what O/S is this?

solaris 10

 mount
/ on /dev/md/dsk/d10 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=154000a on Thu May 14 11:45:04 2015
/devices on /devices read/write/setuid/devices/dev=45c0000 on Thu May 14 11:43:47 2015
/system/contract on ctfs read/write/setuid/devices/dev=4600001 on Thu May 14 11:43:47 2015
/proc on proc read/write/setuid/devices/dev=4640000 on Thu May 14 11:43:47 2015
/etc/mnttab on mnttab read/write/setuid/devices/dev=4680001 on Thu May 14 11:43:47 2015
/etc/svc/volatile on swap read/write/setuid/devices/xattr/dev=46c0001 on Thu May 14 11:43:47 2015
/system/object on objfs read/write/setuid/devices/dev=4700001 on Thu May 14 11:43:47 2015
/lib/libc.so.1 on /usr/lib/libc/libc_hwcap2.so.1 read/write/setuid/devices/dev=154000a on Thu May 14 11:45:03 2015
/dev/fd on fd read/write/setuid/devices/dev=48c0001 on Thu May 14 11:45:04 2015
/var on /dev/md/dsk/d20 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=1540014 on Thu May 14 11:45:06 2015
/tmp on swap read/write/setuid/devices/xattr/dev=46c0002 on Thu May 14 11:45:06 2015
/var/run on swap read/write/setuid/devices/xattr/dev=46c0003 on Thu May 14 11:45:06 2015
/u01 on /dev/dsk/c2t0d0s5 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=740085 on Thu May 14 11:46:50 2015
/u02 on /dev/dsk/c2t1d0s5 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=7400c5 on Thu May 14 11:46:50 2015
/sim9 on /dev/dsk/c4t21d0s6 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=740546 on Thu May 14 11:46:50 2015
/sim8 on /dev/dsk/c4t20d0s6 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=740506 on Thu May 14 11:46:50 2015
/sim7 on /dev/dsk/c4t19d0s6 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=7404c6 on Thu May 14 11:46:51 2015
/sim6 on /dev/dsk/c4t25d0s6 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=740646 on Thu May 14 11:46:51 2015
/sim3 on /dev/dsk/c4t15d0s6 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=7403c6 on Thu May 14 11:46:51 2015
/sim1 on /dev/dsk/c4t13d0s6 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=740346 on Thu May 14 11:46:51 2015
/sim4 on /dev/dsk/c4t16d0s6 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=740406 on Thu May 14 11:46:51 2015
/sim2 on /dev/dsk/c4t14d0s6 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=740386 on Thu May 14 11:46:51 2015

So /sim5 ain't mounted (as Scrutinizer and Peasant already said).

Try and mount it manually and see if it complains.

Perhaps need to check the filesystem.

---------- Post updated at 10:50 AM ---------- Previous update was at 10:35 AM ----------

Also, when you tried:

 
 # mount /dev/dsk/c4t24d0s6 /sim5
 

were you in /sim5 at the time? If so, that won't work.

You cannot be in the directory of the mount point when you try to mount.

I was not inside /sim5:

 pwd
/
root@mcelvasp3 # mount /dev/dsk/c4t24d0s6 /sim5
mount: I/O error
mount: Cannot mount /dev/dsk/c4t24d0s6

Try and run a check on the filesystem WITHOUT modifying anything (using the -n switch):

# fsck -F ufs -n /dev/rdsk/c4t24d0s6

That should tell you whether the system thinks there's a filesystem there and, if so, how much damage, if any, it has.

Was anything else in /sim5? Try:-

find /sim5 -type d -exec fuser {} \;

You might hit your own process as the find progresses, of course. You might need to give the full path the fuser depending on $PATH

I've use a find in case there is a directory structure in there and someone has navigated their way down there.

Robin

I think that this might even tell you where it was last mounted if it is a valid filesystem.

Robin

using

fsck

turns out

fsck -F ufs -n /dev/rdsk/c4t24d0s6
Can't open /dev/rdsk/c4t24d0s6: I/O error
You have new mail in /var/mail//root

and using the find:

find /sim5 -type d -exec fuser {} \;
/sim5:    19135o
root@mcelvasp3 # pwd
/
root@mcelvasp3 #

Can we assume that process 19135 was your find? Is there process still there?

The error from fsck suggests something more worrying altogether.

Robin

Looks like a failed disk.

Is this local disk without RAID protection ?

I can see that root / is installed on md device, probably using RAID protection...

I really dont think is a disk issue, because we are using NetApp as storage for this server

Are you using FC multipath ?

Check output of :
fcinfo hba-port

Look for State, should be online for every card/port to which is connected to FC switch or directly to storage.

Unfortunately, i have no experience with netapp to offer assistance there, but i do see that you are not using native solaris multipath.

Is that sarcasm?

I apologise if you think it was sarcasm, It was not, I said that because when you use NetApp, you use the disks to create LUNs, so that

/dev/rdsk/c4t24d0s6

is actually a LUN.

In fact for this partcular server, we are not using FC, instead we are using iscsi, so all iscsi targets are online:

 iscsiadm list target
Target: iqn.1992-08.com.netapp:sn.118055693
        Alias: -
        TPGT: 2000
        ISID: 4000002a0000
        Connections: 1
Target: iqn.1992-08.com.netapp:sn.1574168032
        Alias: -
        TPGT: 1005
        ISID: 4000002a0000
        Connections: 1
Target: iqn.1992-08.com.netapp:sn.142241490
        Alias: -
        TPGT: 1000
        ISID: 4000002a0000
        Connections: 1