Sorry to followup to my own email but I eventually solved my problem by reformatting the filesystem and copying all the data back to it.  I just couldn't get the security set right.  I could mount the share, but not see any files on it.  From that point I reformatted, without doing anything else, and everything worked fine from then on.
<br><br>THanks.<br><br>---------- Forwarded message ----------<br><span class="gmail_quote">From: <b class="gmail_sendername">Jim Dibb</b> &lt;<a href="mailto:jimdibb@gmail.com">jimdibb@gmail.com</a>&gt;<br>Date: Mar 7, 2006 8:00 PM
<br>Subject: Re: [Wlug] problems with smb export on external usb drive<br>To: Worcester Linux Users Group &lt;<a href="mailto:wlug@mail.wlug.org">wlug@mail.wlug.org</a>&gt;<br><br></span><div style="direction: ltr;"><br><br>
<div></div><div style="direction: ltr;"><span class="q"><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style="direction: ltr;">
<div style="direction: ltr;">
<span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">&gt; &gt; &gt;<br>&gt; &gt; &gt; Great answer, that was it.&nbsp;&nbsp;Only question I have is whether I have to
<br>&gt; disable SeLinux control of smbd and nmbd or just smbd.&nbsp;&nbsp;Thanks!<br><br>Those aren't really the proper answer.&nbsp;&nbsp;The correct solution is to
<br>label the filesystem for smbd access, or add the desired filesystem<br>label to the policy.<br><br>But I suppose your solution is ok, akin to disabling a firewall<br>instead of unblocking the one port you need.</blockquote>

</span></div></div></blockquote></span></div><div style="direction: ltr;"><div style="direction: ltr;"><br>
 </div><br></div><br>

</div>