Steinar H. Gunderson wrote: [Sat Jul 28 2007, 08:45:47PM EDT]
> Uhm, why do you want to export your /proc? I'm unsure if that's supported at
> all. In any case, the severity massively inflated -- I assume you meant
> "grave" and not "serious", but not being able to export bind-mounted /proc
> surely does not make the entire package unusable or nearly so.
I don't want to export my /proc, I want to export a filesystem that
has proc mounted on a subdir.
Consider an NFS-root structure:
/chroots/foo/proc
/chroots/foo/sys
/chroots/foo/usr
/chroots/foo/lib
/chroots/foo/etc
/chroots/foo/dev
/chroots/foo/tmp
This is exported via
/chroots/foo 10.0.0.0/8(ro,no_root_squash,no_subtree_check)
(It's read-only because the client uses unionfs to make a writeable
tmpfs over the NFS-root.)
On the server I like to do fast builds and such. So I treat it like
a chroot there and bind-mount important dirs.
/dev/mapper/raid_vg-foo /chroots/foo ext3 noatime 0 2
/dev /chroots/foo/dev none bind 0 0
/dev/pts /chroots/foo/dev/pts devpts defaults 0 0
/dev/shm /chroots/foo/dev/shm none bind 0 0
/home/agriffis /chroots/foo/home/agriffis none bind 0 0
/proc /chroots/foo/proc none bind 0 0
/sys /chroots/foo/sys none bind 0 0
/tmp /chroots/foo/tmp none bind 0 0
This is quite a common scenario when working on large-scale NFS-root
installations. This worked well with 1.0.9 but has stopped working
with 1.1.0 because of the NFS server freeze when it encounters the
bind-mounted proc dir.
In fact I determined it also freezes when proc is mounted directly,
nevermind bind-mounting. My original report said that it worked in
that configuration, but it doesn't.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
