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.
I'm a little bit confused because I thought that NFS should work on
filesystem and should not care about devices, but it seems that it's not
true.
Is here someone who is interested in this problematic and know whether
this is bug or feature? I've done lots of googling, but had not found
anything relevant :(
Many thanks in advance...
--
Martin Filip
e-mail: [email protected]
ICQ#: 31531391
jabber: [email protected]
________________________________________
/ BOFH Excuse #274: It was OK before you \
\ touched it. /
----------------------------------------
\ ,__,
\ (oo)____
(__) )\
||--|| *
-
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]
