Thanks for the reply.
This client suits our environment. Do you have any link, which says this?
On Wed, Nov 5, 2014 at 12:10 PM, Dilger, Andreas
wrote:
> 2.1.1 is a very old release. Did you try newer clients? It may well be
> that this is a spurious error message that was turned off in newer
2.1.1 is a very old release. Did you try newer clients? It may well be that
this is a spurious error message that was turned off in newer releases.
Cheers, Andreas
On Nov 3, 2014, at 7:06, "Pankaj Dorlikar"
mailto:pankaj.dorli...@gmail.com>> wrote:
thanks for the responce.The issue is that th
thanks for the responce.The issue is that these (mentioned) messages are
continuously getting logged in /var/log/messages.
On Mon, Nov 3, 2014 at 4:40 PM, Parinay Kondekar <
parinay.konde...@seagate.com> wrote:
> 391 #define>EACCES> > 13> /* Permission denied */
>
> What problem are you
391 #define>EACCES> > 13> /* Permission denied */
What problem are you facing ?
HTH
On Mon, Nov 3, 2014 at 3:28 PM, Pankaj Dorlikar
wrote:
>
> HI,
>
> we have cent os 6.2 (x_64) installed node where we are observing below
> messages
>
HI,
we have cent os 6.2 (x_64) installed node where we are observing below
messages
##
Nov 3 15:09:42 node3 kernel: LustreError:
6491:0:(mdc_locks.c:722:mdc_enqueue()) ldlm_cli_enqueue: -13
Nov 3 15:09:42 node3 kernel: LustreError:
6491:0:(
On Fri, 2010-01-15 at 10:09 -0800, Jagga Soorma wrote:
> Hi Guys,
Hi Jagga,
> Jan 14 17:06:36 resmds01 kernel: Lustre:
> 7790:0:(client.c:1383:ptlrpc_expire_one_request()) @@@ Request
> x1324894173265938 sent from reshpcfs-OST0001-osc to NID 10.0.250...@o2ib3 0s
> ago has failed due to network
Hi Guys,
I just deployed a new lustre filesystem and was unable to mount the
filesystem on a client for the first time. I was able to reach everything
using the:
lctl ping i...@o2ib3
All networks were up but the client hanged while doing a mount. So, I
decided to reboot my client and was then
