linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Bryan Schumaker <bjschuma@netapp.com>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/2] Changes in 3.1 kernel break NFS monitoring tools
Date: Wed, 21 Sep 2011 14:31:12 -0400	[thread overview]
Message-ID: <4E7A2D70.6000400@RedHat.com> (raw)
In-Reply-To: <4E7A2C27.8020209@netapp.com>



On 09/21/2011 02:25 PM, Bryan Schumaker wrote:
> On 09/21/2011 02:16 PM, Steve Dickson wrote:
>> Both parser of nfsiostat and mountstats depend on the 
>> the first word in /proc/self/mountstats to be 'device'
>> for them to parse through all the devices. 
>>
>> NFS mounts entries,  in 3.1,  no longer have start with
>> the word 'device'. They start with the actual device, 
>> which confused both set of parsing routines.
> 
> I sent in a patch to fix this on the kernel end almost a month ago, but it must have gotten lost with the kernel.org confusion.  I included what I came up with below
Interesting... Maybe we should still apply these patches until
your patch shows up? They are definitely broken... 

steved.
.
> 
> - Bryan
> 
> [PATCH] VFS: Add "device" tag to /proc/self/mountstats
> 
> nfsiostat was failing to find mounted filesystems on kernels after
> 2.6.38 because of changes to show_vfsstat() by commit
> c7f404b40a3665d9f4e9a927cc5c1ee0479ed8f9.  This patch adds back the
> "device" tag before the nfs server entry so scripts can parse the
> mountstats file correctly.
> 
> Signed-off-by: Bryan Schumaker <bjschuma@netapp.com>
> ---
>  fs/namespace.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/fs/namespace.c b/fs/namespace.c
> index 22bfe82..1429114 100644
> --- a/fs/namespace.c
> +++ b/fs/namespace.c
> @@ -1109,6 +1109,7 @@ static int show_vfsstat(struct seq_file *m, void *v)
>  
>  	/* device */
>  	if (mnt->mnt_sb->s_op->show_devname) {
> +		seq_puts(m, "device ");
>  		err = mnt->mnt_sb->s_op->show_devname(m, mnt);
>  	} else {
>  		if (mnt->mnt_devname) {
> 
> 
>>
>> Steve Dickson (2):
>>   nfsiostat: Breaks on 3.1 kernels
>>   mountstats: Breaks on 3.1 kernels
>>
>>  tools/mountstats/mountstats.py |    9 +++++++++
>>  tools/nfs-iostat/nfs-iostat.py |   11 +++++++++--
>>  2 files changed, 18 insertions(+), 2 deletions(-)
>>
> 

  reply	other threads:[~2011-09-21 18:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21 18:16 [PATCH 0/2] Changes in 3.1 kernel break NFS monitoring tools Steve Dickson
2011-09-21 18:16 ` [PATCH 1/2] nfsiostat: Breaks on 3.1 kernels Steve Dickson
2011-09-21 18:16 ` [PATCH 2/2] mountstats: " Steve Dickson
2011-09-21 18:25 ` [PATCH 0/2] Changes in 3.1 kernel break NFS monitoring tools Bryan Schumaker
2011-09-21 18:31   ` Steve Dickson [this message]
2011-09-21 18:51     ` Chuck Lever
2011-09-21 19:03       ` Bryan Schumaker
     [not found]     ` <4E7A2D70.6000400-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2011-09-21 18:51       ` J. Bruce Fields
2011-09-21 19:31         ` Steve Dickson
2011-09-21 19:34           ` Bryan Schumaker

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=4E7A2D70.6000400@RedHat.com \
    --to=steved@redhat.com \
    --cc=bjschuma@netapp.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 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).