<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 10/17/13 8:46 AM, Dan Wilga wrote:<br>
</div>
<blockquote cite="mid:525FDC12.3000106@dwilga-linux1.amherst.edu"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 10/16/13 11:33 PM, Phill Edwards
wrote:<br>
</div>
<blockquote
cite="mid:CAE2RtTMr-NLB1C9gOHW8Z1Ane4NNjeSpXNuX1oeQgOUerensbg@mail.gmail.com"
type="cite">
<div dir="ltr">I am no expert at all with NFS, but I just
checked my working<br>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
/etc/exports, and the thing that I can see that is
different is the<br>
fsid values. Your first (root) entry should be fsid=0,
and all the<br>
others should be different integer values. The fsid
identifies the<br>
filesystem and has to be different for each entry. I
just have mine<br>
as 0, 1, and 2.<br>
<div class="HOEnZb">
<div class="h5"><br>
</div>
</div>
</blockquote>
<div> </div>
<div>Thanks so much, you hit the nail right on the head!
The problem was indeed because I had duplicate fsid
values. Are you sure you're not an expert :) </div>
</div>
</div>
</div>
<br>
</blockquote>
I've been using NFS for many years, and have never seen a need for
the fsid parameter. IMHO, it's probably best to just leave it out
and let NFS derive a number by itself. It will use either the UUID
or the device number. It's only in the rare case where a
particular device has neither of these that you need to add this
parameter.<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
</pre>
</blockquote>
To tell the truth, my other NFS points don't use fsid, only the one
on the large fakeraid. Can't recall *why* I ended up resorting to
fsid, might have been that the device number wasn't usable by nfsd
to derive its own number though.<br>
An example of my other exports file entries is below:<br>
/var/lib/mythtv/recordings
192.168.0.0/24(ro,async,no_root_squash,no_subtree_check)<br>
I toyed with the notion of setting it rw, but as I don't write to
those directories from remote systems, I didn't bother.<br>
If I need to manually write to those directories, I'll do it via my
ssh session.<br>
</body>
</html>