linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Johannes Schild" <JSchild@gmx.de>
To: Peng Tao <tao.peng@emc.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: RE: Blocklayout
Date: Fri, 10 Aug 2012 11:20:16 +0200	[thread overview]
Message-ID: <20120810092016.177360@gmx.net> (raw)
In-Reply-To: <CA+a=Yy6C-d82MR6Lun4sRcJ0euBBpf0Ra3cHDnQ8eKENi5eU2Q@mail.gmail.com>

Hi Tao,

> > [59260.324598] encoding getdevicelist!
> > [59260.324600] decode_getdevicelist: num_dev 1
> > [59260.324601] nfs41_sequence_done: Error 0 free the slot
> > [59260.324602] nfs4_free_slot: slotid 16 highest_used_slotid -1
> > [59260.324605] <-- _nfs4_getdevicelist status=0
> > [59260.324606] nfs4_proc_getdevicelist: err=0, num_devs=1
> > [59260.324607] bl_set_layoutdriver GETDEVICELIST numdevs=1, eof=1
> > [59260.324608] nfs4_blk_get_deviceinfo max_resp_sz 135168 max_pages 33
> > [59260.324629] nfs4_blk_get_deviceinfo: dev_id:
> The deviceid field returned by server is empty. That's why device
> discovery failed.

Is the deviceid the field where the signature, created with parted, should be stored?

 
> > [59260.324630] --> _nfs4_proc_getdeviceinfo
> > [59260.324632] --> nfs41_call_sync_prepare data->seq_server
> ffff88003c8d7800
> > [59260.324633] --> nfs4_setup_sequence clp ffff88003c733400 session
> ffff88003c733c00 sr_slot -1
> > [59260.324634] --> nfs41_setup_sequence
> > [59260.324635] --> nfs4_find_slot used_slots=0000
> highest_used=4294967295 max_slots=16
> > [59260.324636] <-- nfs4_find_slot used_slots=0001 highest_used=0
> slotid=0
> > [59260.324637] <-- nfs41_setup_sequence slotid=0 seqid=9
> > [59260.324638] <-- nfs4_setup_sequence status=0
> > [59260.324642] encode_sequence: sessionid=1344524732:4:4:0 seqid=9
> slotid=0 max_slotid=0 cache_this=0
> > [59260.333545] nfs41_sequence_done: Error 0 free the slot
> > [59260.333547] nfs4_free_slot: slotid 16 highest_used_slotid -1
> > [59260.333553] <-- _nfs4_proc_getdeviceinfo status=0
> > [59260.333555] nfs4_blk_get_deviceinfo getdevice info returns 0
> > [59260.333572] nfs4_blk_decode_device CREATING PIPEFS MESSAGE
> > [59260.333573] nfs4_blk_decode_device: deviceid: , mincount: 136
> Here shows the same error.
> 
> You may check server code to see if there is something wrong with
> getdevicelist proc handling.
>

I am not experienced enough to check this i think. Is there other server code than "ctl" (on the howto)?

> Cheers,
> Tao

Thanks

Johannes

  reply	other threads:[~2012-08-10  9:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08 15:58 Blocklayout Johannes Schild
2012-08-08 16:39 ` Blocklayout Jim Rees
2012-08-08 18:26   ` Blocklayout Johannes Schild
2012-08-09  8:42     ` Blocklayout Johannes Schild
2012-08-09  8:56       ` Blocklayout Peng, Tao
2012-08-09 15:27         ` Blocklayout Johannes Schild
2012-08-09 17:12           ` Peng Tao
2012-08-10  7:48             ` Johannes Schild
2012-08-10  8:29               ` Peng Tao
2012-08-10  9:20                 ` Johannes Schild [this message]
2012-08-10  9:51                   ` Peng Tao
2012-08-10 12:06                     ` Johannes Schild
2012-08-10 12:18                       ` Jim Rees
2012-08-10 13:00                         ` Johannes Schild
2012-08-13 19:50                           ` Johannes Schild
2012-08-14 14:09                             ` Peng Tao

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=20120810092016.177360@gmx.net \
    --to=jschild@gmx.de \
    --cc=linux-nfs@vger.kernel.org \
    --cc=tao.peng@emc.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;
as well as URLs for NNTP newsgroup(s).