Topic
  • 3 replies
  • Latest Post - ‏2013-11-23T06:30:07Z by yuri
tomcat0112
tomcat0112
10 Posts

Pinned topic Automount gpfs filesystem on windows

‏2013-11-19T02:08:27Z |

Hello all:

I have a gpfs cluster on linux, I add a window node as client to this cluster successfully.

but when I mmmount gpfs filesystem, it couldn't mount.

At last, I mount gpfs filesystem successfully, using  "mmwinmount mount gpfs_src Z -N clinetnode1" .

But the gpfs filesystem cann't automount when I issue "mmmount all -a".

the gpfs filesystem :

-A automount

-T /gpfs_src

-t Z

How to solve this problem?

  • vpaul
    vpaul
    81 Posts

    Re: Automount gpfs filesystem on windows

    ‏2013-11-19T05:43:48Z  

    Hello,

    mmmount is a wrapper around mmwinmount. It does a lot more than just mmwinmount. It is a good sign that mmwinmount works on the Windows node.

    - Are you able to access Z: after the successful mmwinmount? 

    - Next, have you tried "mmmount gpfs_src" on the Windows node?

    - If that works, try "mmmount gpfs_src -N clientnode1" on the Windows node

    - If successful till now, try "mmmount gpfs_src -a" from a Linux node. If this fails to mount Z: on the Windows node, then it is likely a ssh related issue between Linux and Windows node.

    -Vipul

  • tomcat0112
    tomcat0112
    10 Posts

    Re: Automount gpfs filesystem on windows

    ‏2013-11-20T13:21:51Z  
    • vpaul
    • ‏2013-11-19T05:43:48Z

    Hello,

    mmmount is a wrapper around mmwinmount. It does a lot more than just mmwinmount. It is a good sign that mmwinmount works on the Windows node.

    - Are you able to access Z: after the successful mmwinmount? 

    - Next, have you tried "mmmount gpfs_src" on the Windows node?

    - If that works, try "mmmount gpfs_src -N clientnode1" on the Windows node

    - If successful till now, try "mmmount gpfs_src -a" from a Linux node. If this fails to mount Z: on the Windows node, then it is likely a ssh related issue between Linux and Windows node.

    -Vipul

    - Are you able to access Z: after the successful mmwinmount? 

    yes, i can access Z.

    - Next, have you tried "mmmount gpfs_src" on the Windows node?

    yes, but it shows error:

    Thu Nov 14 15:12:36 HKT 2013: 6027-1623 mmmount: Mounting file systems ...
    clientnode1:  mmremote: Unable to mount /dev/gpfs_src_small on drive X.
    clientnode1:      The drive letter appears to be in use.  Unmounting /dev/gpfs_src_small
    mmmount: 6027-1639 Command failed.  Examine previous error messages to determine cause.

     

     

     

  • yuri
    yuri
    213 Posts

    Re: Automount gpfs filesystem on windows

    ‏2013-11-23T06:30:07Z  

    - Are you able to access Z: after the successful mmwinmount? 

    yes, i can access Z.

    - Next, have you tried "mmmount gpfs_src" on the Windows node?

    yes, but it shows error:

    Thu Nov 14 15:12:36 HKT 2013: 6027-1623 mmmount: Mounting file systems ...
    clientnode1:  mmremote: Unable to mount /dev/gpfs_src_small on drive X.
    clientnode1:      The drive letter appears to be in use.  Unmounting /dev/gpfs_src_small
    mmmount: 6027-1639 Command failed.  Examine previous error messages to determine cause.

     

     

     

    "The drive letter appears to be in use" message means that GPFS has performed a mount, but the drive letter assigned by Windows wasn't the one that was requested.  One can only speculate why this may be.  Perhaps some sort of virtual disk driver is loaded, e.g. Virtual Clone Drive or VirtualCD?  Those usually grab Z: by default, and this may come into play even when no image is mounted.  

    I'd simply try a different drive letter.

    yuri