On Monday June 26, [email protected] wrote:
> Hello to LKML,
>
> few days ago I've changed my sw RAID5 to use md_d devices, which are
> "partitonable". (major 254, minor dependant on partiton no)
>
> The problem is with kernel space NFS daemon. When I create loopback
> device and export it - everything works OK, but when exported directory
> is directly something goes really wrong and it's not possible to mount
> it.
>
> I'm getting "nfs: server 192.168.0.2 not responding, timed out" in my
> kernel log, when I look on what's happening on network, the last thing
> what's there are 3 retransmitted GETATTR calls without any response.
Odd. It works fine for me (I've had this sort of configuration on
some machines for ages, and I just tested a bleeding edge kernel and
it still works).
So I suspect there is something else going on that has nothing to do
with the usage of partitioned md.... then again, maybe there is some
weird sign extension happening to '254' somewhere, though that would
be terribly strange.
So: details please.
What md device exactly (major and minor)
What filesystem.
'tcpdump -s0' trace capturing all nfs/mountd/rpc packets from before
you issue the mount command. e.g. use 'rpcinfo -p' to find out what
port mountd is listening on then,
tcpdump -s0 -w /tmp/trace host CLIENT and host SERVER and \( \
port 2049 or port 111 or port MOUNTDPORT \) &
Then try the mount.
After the experiment, on the server
grep . /proc/net/rpc/*/content
cat /proc/fs/nfsd/exports
That should be enough detail to start with.
NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
