Hello all,
Not sure if this is the a good place but we are experiencing a strange
issue.
It appears that systemd is un-mounting the file system immediately after
it is mounted.
#strace of systemd shows that the device is not there. Systemd sees
that the path is failed and umounts the device. Our only work around
currently is to link /usr/bin/umount to true. Then the device stays
mounted.
1 stat("/dev/aggr3", {st_mode=S_IFBLK|0644, st_rdev=makedev(239,
235), ...}) = 0
1 readlink("/sys/dev/block/239:235", 0x7ffdb657a750, 1024) = -1
ENOENT (No such file or directory)
1 stat("/sys/dev/block/239:235", 0x7ffdb657a2c0) = -1 ENOENT (No
such file or directory)
1 socket(PF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 19
# It appears that the major min numbers have been changed
[root@gennsd4 system]# ls -l /sys/dev/block/|grep 239
lrwxrwxrwx 1 root root 0 Nov 19 15:04 253:239 ->
../../devices/virtual/block/dm-239
[root@gennsd4 system]# ls -l /dev/aggr3
brw-r--r-- 1 root root 239, 235 Nov 19 15:06 /dev/aggr3
[root@gennsd4 system]# ls /sys/dev/block/239:235
ls: cannot access /sys/dev/block/239:235: No such file or directory
[root@gennsd4 system]# rpm -qa | grep gpfs
gpfs.gpl-4.1.0-7.noarch
gpfs.gskit-8.0.50-32.x86_64
gpfs.msg.en_US-4.1.0-7.noarch
gpfs.docs-4.1.0-7.noarch
gpfs.base-4.1.0-7.x86_64
gpfs.gplbin-3.10.0-229.14.1.el7.x86_64-4.1.0-7.x86_64
gpfs.ext-4.1.0-7.x86_64
[root@gennsd4 system]# rpm -qa | grep systemd
systemd-sysv-219-19.el7.x86_64
systemd-libs-219-19.el7.x86_64
systemd-219-19.el7.x86_64
systemd-python-219-19.el7.x86_64
any help would be appreciated.
Thanks
Matt
____
This email message is a private communication. The information transmitted,
including attachments, is intended only for the person or entity to which it is
addressed and may contain confidential, privileged, and/or proprietary
material. Any review, duplication, retransmission, distribution, or other use
of, or taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is unauthorized by the sender and is
prohibited. If you have received this message in error, please contact the
sender immediately by return email and delete the original message from all
computer systems. Thank you.
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss
