[Lustre-discuss] Newbie - Unable to mount the OST on the Client

[Gupta, Amit]

Thanks Rick,

1) Run "debugfs -c $MGT_DEVICE" on the MGS server, and then cd into the CONFIGS/ directory to check if the "client1-client" config file exists.

[root at mgs]#  debugfs -c -R 'ls -l CONFIGS' /dev/mapper/mpathcp1
debugfs 1.42.12.wc1 (15-Sep-2014)
/dev/mapper/mpathcp1: catastrophic mode - not reading inode or group bitmaps
  32769   40755 (2)      0      0    4096  6-Jan-2015 13:09 .
      2   40755 (2)      0      0    4096  6-Jan-2015 13:10 ..
     12  100644 (1)      0      0   12288  6-Jan-2015 13:10 mountdata
     81  100644 (1)      0      0       0  6-Jan-2015 13:10 params-client
     82  100644 (1)      0      0       0  6-Jan-2015 13:10 params
     83  100644 (1)      0      0   11200  6-Jan-2015 13:10 temp-client
     84  100644 (1)      0      0    9792  6-Jan-2015 13:10 temp-MDT0000
    104  100644 (1)      0      0   10600  6-Jan-2015 13:12 client2-client
    105  100644 (1)      0      0    8880  6-Jan-2015 13:12 client2-OST0000
    107  100644 (1)      0      0   10600  6-Jan-2015 23:38 client1-client
    108  100644 (1)      0      0    8880  6-Jan-2015 23:38 client1-OST0000



2) Run a tool like wireshark to monitor the TCP traffic to see if you can determine where the communication is breaking down

Is there an RPM package for this ? Let me know if you have that information on top of your head else will look for it.

3) Turn up the Lustre debug level to see if it gives you any more information.

Okay


-----Original Message-----
From: Mohr Jr, Richard Frank (Rick Mohr) [mailto:rmohr at utk.edu]
Sent: Wednesday, January 07, 2015 2:12 PM
To: Gupta, Amit
Cc: lustre-discuss at lists.lustre.org
Subject: Re: [Lustre-discuss] Newbie - Unable to mount the OST on the Client

The only other things I can think of at the moment to try are:

1) Run "debugfs -c $MGT_DEVICE" on the MGS server, and then cd into the CONFIGS/ directory to check if the "client1-client" config file exists.

2) Run a tool like wireshark to monitor the TCP traffic to see if you can determine where the communication is breaking down

3) Turn up the Lustre debug level to see if it gives you any more information.

--
Rick Mohr
Senior HPC System Administrator
National Institute for Computational Sciences http://www.nics.tennessee.edu







This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20150107/a9f65dbc/attachment.htm>