Re: [PATCH 0/3] lockd: use per-net refrence-counted NSM clients

2012-09-17 Thread Stanislav Kinsbursky
17.09.2012 19:10, Chuck Lever пишет: On Sep 17, 2012, at 6:49 AM, Stanislav Kinsbursky wrote: 14.09.2012 23:10, Chuck Lever пишет: On Sep 14, 2012, at 1:38 PM, Myklebust, Trond wrote: On Fri, 2012-09-14 at 13:01 -0400, Chuck Lever wrote: What happens if statd is restarted? Nothing

Re: [PATCH 0/3] lockd: use per-net refrence-counted NSM clients

2012-09-17 Thread Chuck Lever
On Sep 17, 2012, at 6:49 AM, Stanislav Kinsbursky wrote: > 14.09.2012 23:10, Chuck Lever пишет: >> >> On Sep 14, 2012, at 1:38 PM, Myklebust, Trond wrote: >> >>> On Fri, 2012-09-14 at 13:01 -0400, Chuck Lever wrote: What happens if statd is restarted? >>> >>> Nothing unusual. Why? >> >>

Re: [PATCH 0/3] lockd: use per-net refrence-counted NSM clients

2012-09-17 Thread Stanislav Kinsbursky
14.09.2012 23:10, Chuck Lever пишет: On Sep 14, 2012, at 1:38 PM, Myklebust, Trond wrote: On Fri, 2012-09-14 at 13:01 -0400, Chuck Lever wrote: What happens if statd is restarted? Nothing unusual. Why? The NSM upcall transport is a potential application for TCP + softconn, now that a

Re: [PATCH 0/3] lockd: use per-net refrence-counted NSM clients

2012-09-17 Thread Stanislav Kinsbursky
14.09.2012 23:10, Chuck Lever пишет: On Sep 14, 2012, at 1:38 PM, Myklebust, Trond wrote: On Fri, 2012-09-14 at 13:01 -0400, Chuck Lever wrote: What happens if statd is restarted? Nothing unusual. Why? The NSM upcall transport is a potential application for TCP + softconn, now that a

Re: [PATCH 0/3] lockd: use per-net refrence-counted NSM clients

2012-09-17 Thread Chuck Lever
On Sep 17, 2012, at 6:49 AM, Stanislav Kinsbursky wrote: 14.09.2012 23:10, Chuck Lever пишет: On Sep 14, 2012, at 1:38 PM, Myklebust, Trond wrote: On Fri, 2012-09-14 at 13:01 -0400, Chuck Lever wrote: What happens if statd is restarted? Nothing unusual. Why? The NSM upcall

Re: [PATCH 0/3] lockd: use per-net refrence-counted NSM clients

2012-09-17 Thread Stanislav Kinsbursky
17.09.2012 19:10, Chuck Lever пишет: On Sep 17, 2012, at 6:49 AM, Stanislav Kinsbursky wrote: 14.09.2012 23:10, Chuck Lever пишет: On Sep 14, 2012, at 1:38 PM, Myklebust, Trond wrote: On Fri, 2012-09-14 at 13:01 -0400, Chuck Lever wrote: What happens if statd is restarted? Nothing

Re: [PATCH 0/3] lockd: use per-net refrence-counted NSM clients

2012-09-14 Thread Chuck Lever
On Sep 14, 2012, at 1:38 PM, Myklebust, Trond wrote: > On Fri, 2012-09-14 at 13:01 -0400, Chuck Lever wrote: >> What happens if statd is restarted? > > Nothing unusual. Why? The NSM upcall transport is a potential application for TCP + softconn, now that a persistent rpc_clnt is used. It

Re: [PATCH 0/3] lockd: use per-net refrence-counted NSM clients

2012-09-14 Thread Myklebust, Trond
On Fri, 2012-09-14 at 13:01 -0400, Chuck Lever wrote: > What happens if statd is restarted? Nothing unusual. Why? > Sent from my iPhone > > On Sep 14, 2012, at 10:25 AM, Stanislav Kinsbursky > wrote: > > > This is a bug fix for https://bugzilla.redhat.com/show_bug.cgi?id=830862. > > > > The

Re: [PATCH 0/3] lockd: use per-net refrence-counted NSM clients

2012-09-14 Thread Chuck Lever
What happens if statd is restarted? Sent from my iPhone On Sep 14, 2012, at 10:25 AM, Stanislav Kinsbursky wrote: > This is a bug fix for https://bugzilla.redhat.com/show_bug.cgi?id=830862. > > The problem is that with NFSv4 mount in container (with separated mount > namesapce) and active

[PATCH 0/3] lockd: use per-net refrence-counted NSM clients

2012-09-14 Thread Stanislav Kinsbursky
This is a bug fix for https://bugzilla.redhat.com/show_bug.cgi?id=830862. The problem is that with NFSv4 mount in container (with separated mount namesapce) and active lock on it, dying child reaped of this container will try to umount NFS and doing this will try to create RPC client to send

[PATCH 0/3] lockd: use per-net refrence-counted NSM clients

2012-09-14 Thread Stanislav Kinsbursky
This is a bug fix for https://bugzilla.redhat.com/show_bug.cgi?id=830862. The problem is that with NFSv4 mount in container (with separated mount namesapce) and active lock on it, dying child reaped of this container will try to umount NFS and doing this will try to create RPC client to send

Re: [PATCH 0/3] lockd: use per-net refrence-counted NSM clients

2012-09-14 Thread Chuck Lever
What happens if statd is restarted? Sent from my iPhone On Sep 14, 2012, at 10:25 AM, Stanislav Kinsbursky skinsbur...@parallels.com wrote: This is a bug fix for https://bugzilla.redhat.com/show_bug.cgi?id=830862. The problem is that with NFSv4 mount in container (with separated mount

Re: [PATCH 0/3] lockd: use per-net refrence-counted NSM clients

2012-09-14 Thread Myklebust, Trond
On Fri, 2012-09-14 at 13:01 -0400, Chuck Lever wrote: What happens if statd is restarted? Nothing unusual. Why? Sent from my iPhone On Sep 14, 2012, at 10:25 AM, Stanislav Kinsbursky skinsbur...@parallels.com wrote: This is a bug fix for

Re: [PATCH 0/3] lockd: use per-net refrence-counted NSM clients

2012-09-14 Thread Chuck Lever
On Sep 14, 2012, at 1:38 PM, Myklebust, Trond wrote: On Fri, 2012-09-14 at 13:01 -0400, Chuck Lever wrote: What happens if statd is restarted? Nothing unusual. Why? The NSM upcall transport is a potential application for TCP + softconn, now that a persistent rpc_clnt is used. It just