Hi Guys,
This one has got me completely baffled and after some fairly lengthy searching online and in the forum, I think I should share this with you - after all someone is bound to have seen this?
So the story so far, I've built a couple of RHEL 7.5 servers, these are HP DL360 G10's with two six core Xeon, 4 * 300Gb SSD and 64Gb RAM along with 6 network connections in bonds - all good so far.
While building the test server I lost a couple of directories to the same fault and effectively just recreated the box from an image due to time constraints.
However, I now have the problem again and am getting ready to go out in the carpark with the other SA and perform the formation headless chicken dance. The problem shows up as follows on both XFS and in this case a CIFS mount.
Mount the Share;
mount -t cifs -o username=XXXXXX,password=XXXXXX,dir_mode=0775,uid=520,gid=500 //CATHNAS01/SP_DB_EXP /mnt
This bit works and gives;
fbakirpomp2 (root) /-> df -h /mnt
Filesystem Size Used Avail Use% Mounted on
//CATHNAS01/SP_DB_EXP 1.5T 1000G 501G 67% /mnt
fbakirpomp2 (root) /->
fbakirpomp2 (root) /-> ls -l / | grep mnt
drwxrwxr-x 1 oraogi dba 0 Nov 12 16:40 mnt
drwxr-xr-x 2 root root 4096 Oct 3 2016 mnt1
fbakirpomp2 (root) /->
All good so far;
However after a little while (on the machine with the problem) we get;
[root@fbakirpomp3 ~]# df -h /mnt
df: '/mnt': No such device or address
[root@fbakirpomp3 ~]# ls -l / | grep mnt
ls: cannot access /mnt: No such device or address
d?????????? ? ? ? ? ? mnt
[root@fbakirpomp3 ~]#
So it would seem that the mountpoint has really got itself in a panic, any pointes here would be handy.
The RHEL 7.5 install exhibits this "feature" in the version installed straight from media and the version where I have patched from the RHSM repo with the following command.
yum install yum-plugin-versionlock
yum --releasever=7.5 update
So if anyone has seen this problem or has any pointers I'd be very grateful.
Regards
Gull04
hist