Erik Bryer wrote: > > I've tried this many times, read the faq, and so on. Do I misunderstand? Is the st_dev, "ID of device containing file", as read on the client not going to be the same as what is forced by "fsid=n" in the exports file? > > No, they are *different* IDs. The Linux NFS server's fsid is for export purpose (used to construct NFS file handler). It has *nothing* to do with "st_dev" obtained from "stat" system call (that is used by Linux VFS layer). To display the linux (nfs) server fsid on client, the easiest way (I think) is probably using some network protocol analyzers that know how to interpret Linux server's file handler (did you try "ethereal" yet ?). If you decode the server's file handler, the fsid you're look for should be there. -- Wendy ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ NFS maillist - NFS@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@xxxxxxxxxxxxxxxxxxxxx is being discontinued. Please subscribe to linux-nfs@xxxxxxxxxxxxxxx instead. http://vger.kernel.org/vger-lists.html#linux-nfs -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
