All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Benny Halevy <bhalevy@tonian.com>
Cc: NFS list <linux-nfs@vger.kernel.org>
Subject: Re: pnfs git tree status pnfs-all-3.1-2011-11-14 pnfs-all-3.2-rc1-2011-11-14
Date: Mon, 14 Nov 2011 11:38:34 -0800	[thread overview]
Message-ID: <4EC16E3A.9040405@panasas.com> (raw)
In-Reply-To: <4EC13EEA.3030404@tonian.com>

On 11/14/2011 08:16 AM, Benny Halevy wrote:
> I merged the following patches into pnfs-all-3.1-2011-11-14
> and rebased the tree onto v3.2-rc1 as pnfs-all-3.2-rc1-2011-11-14.
> 
> pnfs-block:
>   Peng Tao         e5b35df pnfsblock: cleanup bl_mark_sectors_init
>   Peng Tao         60d5135 pnfsblock: move find lock page logic out of bl_write_pagelist
>   Peng Tao         ab0c07d pnfsblock: set read/write tk_status to pnfs_error
>   Peng Tao         85e8c84 pnfsblock: remove rpc_call_ops from struct parallel_io
>   Peng Tao         7c93c37 pnfsblock: clean up _add_entry
>   Peng Tao         ec11faf pnfsblock: alloc short extent before submit bio
> 
> pnfsd:
>   Boaz Harrosh     5e57e48 SQUASHME: pnfsd: Don't call fs_layout_return on a none-file
> 

What happened to the PNFSD dbg Channel. Was that submitted before?

Boaz 

> spnfs-block:
>   Benny Halevy     400ab8f SQUASHME: spnfs-block: fix oops in device_slice
>   Benny Halevy     bd6bc0a SQUASHME: spnfs-block: add dprints for device_slice
> 
> Both versions pass connectathon tests against pnfsd-lexp server using the files layout.
> 
> Block layout fails as the server ctl process crashes as follows:
> 
> kernel: nfsv4 compound op #2/2: 47 (OP_GETDEVICEINFO)
> kernel: nfsd4_getdevinfo: layout_type 3 dev_id 28d:1f maxcnt 135168
> kernel: nfsd4_getdevinfo: sb ffff88002c535cd0
> kernel: pnfs_set_device_notify: -->
> kernel: renewing client (clientid 4ec13510/00000003)
> kernel: pnfs_set_device_notify: Incr device count (clnt ffff88002d310000) to 2
> kernel: nfsd4_encode_getdevinfo: err 0
> kernel: device_slice: dev_id=0:31
> kernel: device_slice: ret=1
> kernel: ctl[1028]: segfault at 497 ip 00007f74b7909f24 sp 00007fffd2a43948 error 4 in libc-2.13.90.so[7f74b788d000+192000]
> 
> Benny
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  parent reply	other threads:[~2011-11-14 19:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14 16:16 pnfs git tree status pnfs-all-3.1-2011-11-14 pnfs-all-3.2-rc1-2011-11-14 Benny Halevy
2011-11-14 17:23 ` Peng Tao
2011-11-14 17:57   ` Benny Halevy
2011-11-14 19:38 ` Boaz Harrosh [this message]
2011-11-15  4:11   ` Benny Halevy
2011-11-15  4:15     ` Benny Halevy
2011-12-04 17:24 ` pnfs git tree status pnfs-all-3.2-rc4-2011-12-04 Benny Halevy
2012-01-09  8:02   ` pnfs git tree status pnfs-all-3.2-2012-01-08 Benny Halevy
2012-01-09 10:38     ` [PATCH] SQUASHME: pnfsd-exofs: Fix the RAID5 export Boaz Harrosh
2012-01-09 10:43       ` Boaz Harrosh
2012-01-11 10:54         ` Benny Halevy
2012-02-23 19:42     ` pnfs git tree status pnfs-all-3.2-2012-02-22 Benny Halevy
2012-05-17 11:29 ` pnfs git tree status pnfs-all-3.4-rc7-2012-05-17 Benny Halevy
2012-05-21 15:44   ` pnfs git tree status pnfs-all-3.4-2012-05-21 Benny Halevy

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=4EC16E3A.9040405@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=bhalevy@tonian.com \
    --cc=linux-nfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.