[gpfsug-discuss] Problems with GPFS on windows 10, stuck at mount. Never mounts.
Vipul Paul
vpaul at us.ibm.com
Tue Nov 6 16:54:38 GMT 2018
Hello Henrik,
I see that you are trying GPFS 4.1.0.4 on Windows 10. This will not work.
You need to upgrade to GPFS 5.0.2 as that is the first release that
supports Windows 10. Please see the FAQ
https://www.ibm.com/support/knowledgecenter/en/STXKQY/gpfsclustersfaq.html#windows
"Starting with V5.0.2, IBM Spectrum Scale additionally supports Windows 10
(Pro and Enterprise editions) in both heterogeneous and homogeneous
clusters. At this time, Secure Boot must be disabled on Windows 10 nodes
for IBM Spectrum Scale to install and function."
Thanks.
--
Vipul Paul | IBM Spectrum Scale (GPFS) Development | vpaul at us.ibm.com |
(503) 747-1389 (tie 997)
From: Lyle Gayne/Poughkeepsie/IBM
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Cc: Vipul Paul/Portland/IBM, Heather J MacPherson/Beaverton/IBM at IBMUS
Date: 11/06/2018 05:46 AM
Subject: Re: [gpfsug-discuss] Problems with GPFS on windows 10,
stuck at mount. Never mounts.
Vipul or Heather should be able to assist.
Thanks,
Lyle
From: "Henrik Cednert (Filmlance)" <henrik.cednert at filmlance.se>
To: "gpfsug-discuss at spectrumscale.org"
<gpfsug-discuss at spectrumscale.org>
Date: 11/06/2018 07:00 AM
Subject: [gpfsug-discuss] Problems with GPFS on windows 10, stuck
at mount. Never mounts.
Sent by: gpfsug-discuss-bounces at spectrumscale.org
Hi there
The welcome mail said that a brief introduction might be in order. So
let’s start with that, just jump over this paragraph if that’s not of
interest. So, Henrik is the name. I’m the CTO at a Swedish film production
company with our own internal post production operation. At the heart of
that we have a 1.8PB DDN MediaScaler with GPFS in a mixed macOS and
Windows environment. The mac clients just use NFS but the Windows clients
use the native GPFS client. We have a couple of successful windows
deployments.
But… Now when we’re replacing one of those windows clients I’m running
into some seriously frustrating ball busting shenanigans. Basically this
client gets stuck on (from mmfs.log.latest) "PM: mounting /dev/ddnnas0” .
Nothing more happens. Just stuck and it never mounts.
I have reinstalled it multiple times with full clean between, removed
cygwin and the root user account and everything. I have verified that
keyless ssh works between server and all nodes, including this node. With
my limited experience I don’t find enough to go on in the logs nor windows
event viewer. I’m honestly totally stuck.
I’m using the same version on this clients as on the others. DDN have
their own installer which installs cygwin and the gpfs packages. Have
worked fine on other clients but not on this sucker. =(
Versions involved:
Windows 10 Enterprise 2016 LTSB
IBM GPFS Express Edition 4.1.0.4
IBM GPFS Express Edition License and Prerequisites 4.1
IBM GPFS GSKit 8.0.0.32
Below is the log from the client. I don’ find much useful at the server,
point me to specific log file if you have a good idea of where I can find
errors of this.
Cheers and many thanks in advance for helping me out here. I’m all ears.
root at M5-CLIPSTER02 ~
$ cat /var/adm/ras/mmfs.log.latest
Mon, Nov 5, 2018 8:39:18 PM: runmmfs starting
Removing old /var/adm/ras/mmfs.log.* files:
mmtrace: The tracefmt.exe or tracelog.exe command can not be found.
mmtrace: 6027-1639 Command failed. Examine previous error messages to
determine cause.
Mon Nov 05 20:39:50.045 2018: GPFS: 6027-1550 [W] Error: Unable to
establish a session with an Active Directory server. ID remapping via
Microsoft Identity Management for Unix will be unavailable.
Mon Nov 05 20:39:50.046 2018: [W] This node does not have a valid extended
license
Mon Nov 05 20:39:50.047 2018: GPFS: 6027-310 [I] mmfsd initializing.
{Version: 4.1.0.4 Built: Oct 28 2014 16:28:19} ...
Mon Nov 05 20:39:50.048 2018: [I] Cleaning old shared memory ...
Mon Nov 05 20:39:50.049 2018: [I] First pass parsing mmfs.cfg ...
Mon Nov 05 20:39:51.001 2018: [I] Enabled automated deadlock detection.
Mon Nov 05 20:39:51.002 2018: [I] Enabled automated deadlock debug data
collection.
Mon Nov 05 20:39:51.003 2018: [I] Initializing the main process ...
Mon Nov 05 20:39:51.004 2018: [I] Second pass parsing mmfs.cfg ...
Mon Nov 05 20:39:51.005 2018: [I] Initializing the page pool ...
Mon Nov 05 20:40:00.003 2018: [I] Initializing the mailbox message system
...
Mon Nov 05 20:40:00.004 2018: [I] Initializing encryption ...
Mon Nov 05 20:40:00.005 2018: [I] Initializing the thread system ...
Mon Nov 05 20:40:00.006 2018: [I] Creating threads ...
Mon Nov 05 20:40:00.007 2018: [I] Initializing inter-node communication
...
Mon Nov 05 20:40:00.008 2018: [I] Creating the main SDR server object ...
Mon Nov 05 20:40:00.009 2018: [I] Initializing the sdrServ library ...
Mon Nov 05 20:40:00.010 2018: [I] Initializing the ccrServ library ...
Mon Nov 05 20:40:00.011 2018: [I] Initializing the cluster manager ...
Mon Nov 05 20:40:25.016 2018: [I] Initializing the token manager ...
Mon Nov 05 20:40:25.017 2018: [I] Initializing network shared disks ...
Mon Nov 05 20:41:06.001 2018: [I] Start the ccrServ ...
Mon Nov 05 20:41:07.008 2018: GPFS: 6027-1710 [N] Connecting to
192.168.45.200 DDN-0-0-gpfs <c0p0>
Mon Nov 05 20:41:07.009 2018: GPFS: 6027-1711 [I] Connected to
192.168.45.200 DDN-0-0-gpfs <c0p0>
Mon Nov 05 20:41:07.010 2018: GPFS: 6027-2750 [I] Node 192.168.45.200
(DDN-0-0-gpfs) is now the Group Leader.
Mon Nov 05 20:41:08.000 2018: GPFS: 6027-300 [N] mmfsd ready
Mon, Nov 5, 2018 8:41:10 PM: mmcommon mmfsup invoked. Parameters:
192.168.45.144 192.168.45.200 all
Mon, Nov 5, 2018 8:41:29 PM: mounting /dev/ddnnas0
--
Henrik Cednert / + 46 704 71 89 54 / CTO / Filmlance
Disclaimer, the hideous bs disclaimer at the bottom is forced, sorry. ?\_(
ツ)_/?
Disclaimer
The information contained in this communication from the sender is
confidential. It is intended solely for use by the recipient and others
authorized to receive it. If you are not the recipient, you are hereby
notified that any disclosure, copying, distribution or taking action in
relation of the contents of this information is strictly prohibited and
may be unlawful._______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20181106/959ca38d/attachment.htm>
More information about the gpfsug-discuss
mailing list