From: Boris Z. (boris@conley.com)
Date: 09/29/98-04:54:37 PM Z
Message-ID: <01BDEBB9.148C5460.boris@conley.com> From: "Boris Z." <boris@conley.com> Subject: RE: management capabilities for NFSv4 Date: Tue, 29 Sep 1998 14:54:37 -0700 By 'active' I mean files with associated locks or shares. Such MIB is not going to replace LOOKUP requests or lookup caches. Using such MIB SNMP manager can display 'active' files and may be issue some related management actions. Carl, what did you want to achieve with such translation? On Tuesday, September 29, 1998 9:14 AM, Dave Hitz [SMTP:hitz@netapp.com] wrote: > > > Can you have a MIB which translates a filehandle to file name? > > > > We can define a well known MIB table for all active filehandle - file name pairs. > > File handles are forever. A client can do a LOOKUP, go quiet for 6 > months, and then come back with a request based on the 6-month-old > filehandle. If the file still exists, the server must honor the > request. Given that, I'm not sure what an "active filehandle" is, > unless you simply mean the filehandle for every file in the system. > (That's a pretty big MIB table to maintain.) > > In addition, arbitrarily translating a file handle (i.e. inode number) > to a file name is not simple for many filesystems. Even if the file > handle was recently LOOKED up, it may be a multi-link file, and the > link through which the LOOKUP occured may have been deleted. In that > case, you basically have to scan all directories in the filesystem to > find the name. > > Dave
This archive was generated by hypermail 2.1.2 : 03/04/05-01:46:26 AM Z CST