On Sun, Aug 05, 2007 at 08:53:08PM +0200, Steinar H. Gunderson wrote:
Hm. I'm trying to reproduce it now, and I can perhaps do it once out of ten.
Sort of hard to track down...
Finally!
I got it to be weird while I was stracing it. From there it was only a
matter of remembering the following
Steinar H. Gunderson wrote: [Sun Aug 05 2007, 02:35:48PM EDT]
This is interesting -- I got home to my testing machine, and
I managed to reproduce it -- but only once. When I restarted
nfs-kernel-server (via the init.d script), the hanging processes
resumed, and from there it was completely
On Sat, Jul 28, 2007 at 08:21:47PM -0400, Aron Griffis wrote:
server
--
mkdir -p /test/proc
mount -o bind /proc /test/proc
echo '/test 10.0.0.0/16(rw,no_root_squash,async,no_subtree_check)'
/etc/exports
exportfs -a
client
--
mkdir /test
mount server:/test /test
/bin/ls
On Sun, Aug 05, 2007 at 02:41:18PM -0400, Aron Griffis wrote:
If I put the server restart in a loop, the client makes slow progress.
Restarting just once does not alleviate the problem forever. It's
possible that I'm seeing it hang once per subdirectory, since I have
a number of mounts under
Hell Aron and Steinar,
Am 2007-07-28 21:15:30, schrieb Aron Griffis:
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
Michelle Konzack wrote: [Fri Aug 03 2007, 07:57:36AM EDT]
Which can not work, since /proc must be the /proc of the machine WHICH
is mounting the nfs-share.
Your statements represent a misreading of the bug. Let's take
a step-by-step approach:
1. The server has /etc/exports:
/foo
On Sat, Jul 28, 2007 at 09:33:38PM -0400, Aron Griffis wrote:
But NFS exports filesystems, so at least in theory, the /proc in there should
be ignored completely unless you export it.
Exactly. But instead it's hanging
Well, nfs-utils does not mess with the mount after it has handed it over to
Package: nfs-kernel-server
Version: 1:1.1.0-11
Severity: serious
--- Please enter the report below this line. ---
When a client attempts to read a bind-mounted proc directory from the
server, the server never responds. Found this with wireshark and
narrowed down to a simple test. Other
severity 435056 normal
thanks
On Sat, Jul 28, 2007 at 08:21:47PM -0400, Aron Griffis wrote:
When a client attempts to read a bind-mounted proc directory from the
server, the server never responds. Found this with wireshark and
narrowed down to a simple test. Other bind-mounts seem to be
Steinar H. Gunderson wrote: [Sat Jul 28 2007, 08:45:47PM EDT]
In any case, the severity massively inflated -- I assume you meant
grave and not serious,
Regarding this part, the NFS server freezing in a situation when it
previously worked is surely a serious error. And I think that the
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
On Sat, Jul 28, 2007 at 09:15:30PM -0400, Aron Griffis wrote:
I don't want to export my /proc, I want to export a filesystem that
has proc mounted on a subdir.
But NFS exports filesystems, so at least in theory, the /proc in there should
be ignored completely unless you export it.
Steinar H. Gunderson wrote: [Sat Jul 28 2007, 09:18:05PM EDT]
On Sat, Jul 28, 2007 at 09:15:30PM -0400, Aron Griffis wrote:
I don't want to export my /proc, I want to export a filesystem that
has proc mounted on a subdir.
But NFS exports filesystems, so at least in theory, the /proc in
13 matches
Mail list logo
