On Mon, Dec 10, 2018 at 02:23:10PM -0500, J. Bruce Fields wrote: > On Mon, Dec 10, 2018 at 01:12:31PM -0500, Jeff Layton wrote: > > On Mon, 2018-12-10 at 12:47 -0500, J. Bruce Fields wrote: > > > We've got a long-standing complaint that tools like lsof, when run on an > > > NFS server, overlook opens and locks held by NFS clients. > > > > > > The information's all there, it's just a question of how to expose it. > > > > > > Easiest might be a single flat file like /proc/locks, but I've always > > > hoped we could do something slightly more structured, using a > > > subdirectory per NFS client. > > > > > > Jeff Layton looked into this several years ago. I don't remember if > > > there was some particular issue or if he just got bogged down in VFS > > > details. > > > > > > > I think I had a patch that generated a single flat file for locks, but > > you wanted to present a directory or file per-client, and I just never > > got around to reworking the earlier patch. > > Oh, OK, makes sense. (But, um, if anyone has a good starting point to recommend to me here, I'm interested. E.g. another pseudofs that's a good example to follow.) --b.
