Sponsored Content
Top Forums UNIX for Advanced & Expert Users Mount Point goes into a very strange state. Post 303041609 by gull04 on Friday 29th of November 2019 03:56:55 AM
Old 11-29-2019
Mount Point goes into a very strange state.

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;

Code:
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;
Code:
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;
Code:
[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.
Code:
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

Last edited by vbe; 11-29-2019 at 07:26 AM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Recover mount point

A disk was sliced into 6 slices with m01 being the mount point for one of the slices. This mount point was deleted with rmdir (ie. rmdir m01). What is the easiest way to recover this mount point? (1 Reply)
Discussion started by: here2learn
1 Replies

2. UNIX for Dummies Questions & Answers

mount point

hi people, I'm trying to create a mount point, but am having no sucess at all, with the following: mount -F ufs /dev/dsk/diskname /newdirectory but i keep getting - mount-point /newdirectory doesn't exist. What am i doing wrong/missing? Thanks Rc (1 Reply)
Discussion started by: colesy
1 Replies

3. UNIX for Dummies Questions & Answers

concept of mount point

Hi All I Know it is a really basic and stupid question perhaps...But I am going bonkers.. I have following valid paths in my unix system: 1. /opt/cdedev/informatica/InfSrv/app/bin 2. /vikas/cdedev/app Both refer to the same physical location. So if I created one file 'test' in first... (3 Replies)
Discussion started by: Vikas Sood
3 Replies

4. UNIX for Advanced & Expert Users

mount point lists

is there any command to know the list of mount points in a server.i need only the mount point lists.i tried using df but it was not helpful.i am using Solaris (1 Reply)
Discussion started by: dr46014
1 Replies

5. Red Hat

NFS mount point

Hi, Can you tell me something about NFS mount point ? Regards, Maddy (3 Replies)
Discussion started by: Maddy123
3 Replies

6. Red Hat

Regarding NFS mount point

Dear All, We have two different mount points in Linux NFS one is 15 TB and another one is 15 TB. Can we club both of the two mount points and club in to a single volume in Linux. As we need to restore Database in that single volume. Kindly help us on this. Regards , rj (10 Replies)
Discussion started by: jegaraman
10 Replies

7. AIX

How to change the mount point of LV?

I have situation where my disk upon reboot, has its mount point as # LOGICAL VOLUME: disk4vol VOLUME GROUP: disk4vg LV IDENTIFIER: 00f609aa00004c0000000152414b786c.1 PERMISSION: read/write VG STATE: active/complete LV STATE: closed/syncd TYPE: jfs2 WRITE VERIFY: off MAX LPs: 512 PP SIZE: 512... (1 Reply)
Discussion started by: mrmurdock
1 Replies

8. Solaris

Sol 10 - Strange NFS behaviour - adminnfs prefix to mount point

Something has changed..... /etc/vfstab entry:- host1:/backup/RMAN - /RMAN nfs - no rw,hard,rsize=32768,wsize=32768,llockBut when I mount it, and run df -k | grep RMANResults are:- host1:/backup/RMAN 54971960832 26752241664 28219719168 49% ... (1 Reply)
Discussion started by: psychocandy
1 Replies

9. UNIX for Beginners Questions & Answers

How to create a new mount point with 600GB and add 350 GBexisting mount point? IN AIX

How to create a new mount point with 600GB and add 350 GBexisting mount point Best if there step that i can follow or execute before i mount or add diskspace IN AIX Thanks (2 Replies)
Discussion started by: Thilagarajan
2 Replies

10. AIX

AIX lsvg strange LV STATE and MOUNT POINT

What does it mean when your LV STATE changes to closed/syncd? What does it mean when your mount point is #? I was not able to mount it or write data to it. So in this case since there was no data in /opt/cvt I used rmlv to get rid of it. Why did I have to manually edit /etc/filesystems to get rid... (1 Reply)
Discussion started by: cokedude
1 Replies
chroot(8)						      System Manager's Manual							 chroot(8)

NAME
chroot - Changes the root directory of a command SYNOPSIS
/usr/sbin/chroot directory command DESCRIPTION
Only root can use the chroot command. The chroot command changes the root directory from / to the specified directory when the command executes. (The command specified includes both the command name as well as any arguments.) Consequently, the root of any path (as indicated by the first / (slash) in the pathname) changes to directory and is always relative to the current root. Even if the chroot command is in effect, directory is relative to the current root of the running process. Several programs may not operate properly after chroot executes. You must ensure that all vital files are present in the new root file system and the relevant pathnames for the files map correctly in the new root file system. For example, the ls -l command fails to give user and group names if the new root file system does not have a copy of the /etc/passwd and /etc/group files. If the /etc/passwd and /etc/group files in the new root file system represent different user and group names, then the output from the ls -l command will be based on those names, not the ones for the system's own name database. Utilities that depend on description files produced by the ctab command may also fail if the required description files are not present in the new root file system. The chroot program uses the execv() function to invoke the specified command. As a consequence, the command specified must be an exe- cutable binary, not a shell script. Further, if the program requires indirect loading (for example, due to unresolved symbols requiring use of a shared library), then /sbin/loader as well as any files it requires (for example, shared libraries) must be present in the new root file system in the appropriate locations. EXAMPLES
To run a subshell with another file system as the root, enter a command similar to the following. Note in this example, the file system is on the /dev/disk/dsk13a device and is mounted to /mnt/dsk13a: chroot /mnt/dsk13a /sbin/sh The command shown in the previous example spec- ifies a change from the current root file system to the one mounted on /mnt/dsk13a while /sbin/sh (which itself is relative to the new root file system) executes. When /bin/sh executes, the original root file system is inaccessible. The file system mounted on /mnt/dsk13a must contain the standard directories of a root file system. In particular, the shell looks for commands in /sbin, /bin, and /usr/bin (among others) on the new root file system. Running the /sbin/sh command creates a subshell that runs as a separate process from the original shell. Press to exit the subshell and return to the original shell. This restores the environment of the original shell, including the meanings of the current directory (.) and the root directory (/). To run a command in another root file system and save the output on the initial root file system, enter a command similar to the following. Note in this example, the file system is on the /dev/disk/dsk13a device and is mounted to /mnt/dsk13a: chroot /mnt/dsk13a /bin/cc -E /u/bob/prog.c > prep.out The previous command runs the /bin/cc command with /mnt/dsk13a as the specified root file system. It compiles the /mnt/dsk13a/u/bob/prog.c file, reads the #include files from the /mnt/dsk13a/usr/include directory, and puts the compiled text in the prep.out file on the initial root file system. To create a file relative to the original root rather than the new one, use this syntax and enter: chroot directory command > file CAUTIONS
If special files in the new root have different major and minor device numbers than the initial root directory, it is possible to overwrite the file system. FILES
Specifies the command path. RELATED INFORMATION
Commands: cc(1), cpp(1), ls(1), sh(1) Functions: chdir(2), chroot(2) exec(2) delim off chroot(8)
All times are GMT -4. The time now is 07:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy