public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Neil Brown <neilb@suse.de>
Cc: Oleg Drokin <green@linuxhacker.ru>, linux-fsdevel@vger.kernel.org
Subject: Re: FS-specified FSID for non-device based filesystems?
Date: Tue, 18 Apr 2006 11:07:08 -0700	[thread overview]
Message-ID: <20060418180708.GB929@kroah.com> (raw)
In-Reply-To: <17475.6724.811707.481414@cse.unsw.edu.au>

On Mon, Apr 17, 2006 at 02:32:04PM +1000, Neil Brown wrote:
> On Sunday April 16, greg@kroah.com wrote:
> > On Mon, Apr 17, 2006 at 10:54:06AM +1000, Neil Brown wrote:
> > >  - filesystems don't have a place in /sys
> > 
> > Then what is /sys/fs/ for?  :)
> 
> good question!
> 
> adams # uname -a 
> Linux adams 2.6.17-rc1-mm1 #298 SMP Tue Apr 11 14:19:52 EST 2006 i686 GNU/Linux
> adams # ls -la /sys/fs
> total 0
> drwxr-xr-x   2 root root 0 Apr 17 14:23 .
> drwxr-xr-x  11 root root 0 Apr 17 14:23 ..
> 
> Doesn't look very useful yet, but I'm hopeful.
> 
> What naming scheme is expected?  i.e. If I want to look at the nfs
> client rpc stats for /import/warehouse,  where would I look?
>   /sys/fs/import/warehouse/nfs/stats
> seems unlikely.
> 
> The idea of putting filesystem stuff in /sys seem to come up on
> linux-kernel every so often and it never seems to get anywhere, often
> because Al Viro pokes obvious holes in the scheme.
> 
> I cannot find anything in Documentation/filesystems/sysfs.txt, so:
> How is /sys/fs supposed to work?

I don't know, as I didn't create it.  I think one of the FUSE developers
did.

thanks,

greg k-h

  reply	other threads:[~2006-04-18 18:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-12 11:10 FS-specified FSID for non-device based filesystems? Oleg Drokin
2006-04-14 20:22 ` Bryan Henderson
2006-04-14 20:45   ` Oleg Drokin
2006-04-14 20:59     ` J. Bruce Fields
2006-04-14 21:32     ` Bryan Henderson
2006-04-14 21:41       ` Oleg Drokin
2006-04-17  0:54 ` Neil Brown
2006-04-17  3:50   ` Greg KH
2006-04-17  4:32     ` Neil Brown
2006-04-18 18:07       ` Greg KH [this message]
2006-04-19 12:15         ` Miklos Szeredi
2006-04-20 11:35           ` Al Viro
2006-04-20 11:58             ` Miklos Szeredi
2006-04-20 12:30               ` Al Viro
2006-04-20 12:43                 ` Miklos Szeredi
2006-04-17  8:00   ` Anton Altaparmakov

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=20060418180708.GB929@kroah.com \
    --to=greg@kroah.com \
    --cc=green@linuxhacker.ru \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=neilb@suse.de \
    /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