From: devzero@web.de
To: NFS@lists.sourceforge.net
Subject: Re: Annoying exports problem
Date: Sun, 18 Feb 2007 17:12:43 +0100 [thread overview]
Message-ID: <1634529243@web.de> (raw)
hi !
>> But maybe the key issue is not so much how it is "meant to work", but
>> how we "want it to work".
>> I suspect it would be very valuable and no harm to allow
>> =
>> /storage *(rw,no_root_squash,async,crossmnt)
>> =
>> to export everything below /storage, including other filesystems.
>
>That's exactly what I was looking for. I see a bunch of references to
>crossmnt basically saying it was never implemented. Maybe still the case?
here`s some loud "i`d like that , too !!!", since i lost the ability to com=
fortably export loopback mounted filesystems (.iso) when switching from one=
distro to a later release, where userspace nfsd was replace by knfsd. my c=
urrent workaround is using unfs3, but that`s a) slow and b) not being bundl=
ed with major distros, so integration of unfs3 is conflicting with bundled =
knfsd and always a pain to setup.
i have solved that "no more than 256 loopback devices available for loopbac=
k mounts"-problem for my huge cd-rom server, by now the only remaining issu=
e to fix is "export every loopback mount below /cd-roms by a single nfs-sha=
re", which shouldn`t be too exotic desire !? :)
regards
roland
On 5/17/06 4:33 PM, "Neil Brown" <neilb@suse.de> wrote:
> On Wednesday May 17, bfields@fieldses.org wrote:
>> On Wed, May 17, 2006 at 04:39:04PM +1000, Neil Brown wrote:
>>> On Tuesday May 16, jeremy@smokehabanos.com wrote:
>>>> I actually got it to work in the little time since my initial post. T=
he
>>>> only way I could do it was to export both the root filesystem and the
>>>> individual directories within the /storage. So it looks like this:
>>>> =
>>>> /storage *(rw,no_root_squash,async)
>>>> /storage/space0 *(rw,no_root_squash,async,no_subtree_check,nohid=
e)
>>>> /storage/space1 *(rw,no_root_squash,async,no_subtree_check,nohid=
e)
>>>> /storage/space2 *(rw,no_root_squash,async,no_subtree_check,nohid=
e)
>>>> /storage/space3 *(rw,no_root_squash,async,no_subtree_check,nohid=
e)
>>>> /storage/space4 *(rw,no_root_squash,async,no_subtree_check,nohid=
e)
>>>> /storage/space5 *(rw,no_root_squash,async,no_subtree_check,nohid=
e)
>>> =
>>> This works too
>>> Putting 'crossmnt' on the first line should remove the need for the
>>> remaining lines.
>> =
>> It should remove the need for the nohide option on those lines, but I
>> think the export lines will still be required. Is that not how it's
>> meant to work?
> =
> Not sure... it is a while since I have looked at that code.
> =
> But maybe the key issue is not so much how it is "meant to work", but
> how we "want it to work".
> I suspect it would be very valuable and no harm to allow
> =
> /storage *(rw,no_root_squash,async,crossmnt)
> =
> to export everything below /storage, including other filesystems.
That's exactly what I was looking for. I see a bunch of references to
crossmnt basically saying it was never implemented. Maybe still the case?
Thanks
-jeremy
> =
> I've put it on my todo list to look into one day.
> =
> NeilBrown
_______________________________________________________________________
Viren-Scan f=FCr Ihren PC! Jetzt f=FCr jeden. Sofort, online und kostenlos.
Gleich testen! http://www.pc-sicherheit.web.de/freescan/?mc=3D022222
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2007-02-18 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-18 16:12 devzero [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-17 5:53 Annoying exports problem Jeremy
2006-05-17 6:17 ` Neil Brown
2006-05-17 6:33 ` Jeremy
2006-05-17 6:39 ` Neil Brown
2006-05-17 7:40 ` Jeremy
2006-05-17 19:26 ` J. Bruce Fields
2006-05-17 23:33 ` Neil Brown
2006-05-17 23:45 ` Jeremy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1634529243@web.de \
--to=devzero@web.de \
--cc=NFS@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox