Linux NFS development
 help / color / mirror / Atom feed
From: marc eshel <eshel.marc@gmail.com>
To: Olga Kornievskaia <aglo@umich.edu>
Cc: Olga Kornievskaia <aglo@umich.edu>,
	schumaker anna <schumaker.anna@gmail.com>,
	linux-nfs <linux-nfs@vger.kernel.org>,
	Trond Myklebust <trondmy@hammerspace.com>,
	"Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>
Subject: pNFS client is not using the stripe value
Date: Fri, 13 Sep 2024 09:46:40 -0700	[thread overview]
Message-ID: <c40a1ed3-0989-44d8-ab3a-9c90f0a9dbad@gmail.com> (raw)
In-Reply-To: <2102290340.59910889.1725952999821.JavaMail.zimbra@desy.de>

This trace on the client shows that it was requested to use *nfl_util 
0x400000*

filelayout_decode_layout: set_layout_map Begin

Sep 13 09:20:10 svl-marcrh-node-1 kernel: nfs4_print_deviceid: device 
id= [3000035a0b38c07df0465]

Sep 13 09:20:10 svl-marcrh-node-1 kernel: filelayout_decode_layout: 
*nfl_util 0x400000* num_fh 1 fsi 0 po 0

Sep 13 09:20:10 svl-marcrh-node-1 kernel: DEBUG: 
filelayout_decode_layout: fh len 61

Sep 13 09:20:10 svl-marcrh-node-1 kernel: --> filelayout_check_layout

Sep 13 09:20:10 svl-marcrh-node-1 kernel: --> filelayout_check_layout 
returns 0

This trace on the DS show that it reads 0x48000 before skipping to 0x880000

So it is skipping *0x400000 *but way was the first chuck 0x48000

Also way some read are 1048576 and most are 524288

gpfsRead enter: gnP 0xFFFF91F810942688 flags 0x1 uioP 0xFFFFAED0C47878B0 
vinfoP 0xFFFF91F81352FA30 off 0 len 1048576

gpfsRead enter: gnP 0xFFFF91F810942688 flags 0x1 uioP 0xFFFFAED0C47878B0 
vinfoP 0xFFFF91F81352FA30 off 1048576 len 524288

gpfsRead enter: gnP 0xFFFF91F810942688 flags 0x1 uioP 0xFFFFAED0CA01F8B0 
vinfoP 0xFFFF91F81352FA30 off 1572864 len 1048576

gpfsRead enter: gnP 0xFFFF91F810942688 flags 0x1 uioP 0xFFFFAED0CA5FB8B0 
vinfoP 0xFFFF91F81352FA30 off 2621440 len 524288

gpfsRead enter: gnP 0xFFFF91F810942688 flags 0x1 uioP 0xFFFFAED0CA01F8B0 
vinfoP 0xFFFF91F81352FA30 off 3145728 len 524288

gpfsRead enter: gnP 0xFFFF91F810942688 flags 0x1 uioP 0xFFFFAED0C47878B0 
vinfoP 0xFFFF91F81352FA30 off 3670016 len 1048576

gpfsRead enter: gnP 0xFFFF91F810942688 flags 0x1 uioP 0xFFFFAED0CA01F8B0 
vinfoP 0xFFFF91F81352FA30 off 8912896 len 524288

Thanks, Marc.


      parent reply	other threads:[~2024-09-13 16:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c4f1d8bf-745b-4a98-9d38-2da4c355d691@gmail.com>
2024-07-29 21:56 ` NFS client failure marc eshel
2024-08-05 21:51   ` NFS client to pNFS DS marc eshel
2024-08-08 14:22     ` Anna Schumaker
2024-08-08 22:07     ` Olga Kornievskaia
2024-08-09 13:06       ` Anna Schumaker
2024-08-09 14:29         ` marc eshel
     [not found]         ` <8ab0fd49-0c90-42bd-a34e-9dcf63a99bd5@gmail.com>
2024-08-09 15:15           ` Olga Kornievskaia
2024-08-09 16:26             ` marc eshel
2024-08-10 21:20               ` Olga Kornievskaia
2024-08-11 19:41                 ` Mkrtchyan, Tigran
2024-08-11 19:50                   ` marc eshel
2024-08-12  6:52                     ` Mkrtchyan, Tigran
2024-08-12 14:37                       ` marc eshel
2024-09-09 23:23                   ` marc eshel
2024-09-10  7:23                     ` Mkrtchyan, Tigran
2024-09-11  5:54                       ` Marc Eshel
2024-09-13 16:46                       ` marc eshel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c40a1ed3-0989-44d8-ab3a-9c90f0a9dbad@gmail.com \
    --to=eshel.marc@gmail.com \
    --cc=aglo@umich.edu \
    --cc=linux-nfs@vger.kernel.org \
    --cc=schumaker.anna@gmail.com \
    --cc=tigran.mkrtchyan@desy.de \
    --cc=trondmy@hammerspace.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox