Good evening, I have problems using RAID5 (md) over nbd. my setup is: host 1 (front end): Kernel 2.4.18 nbd-client (nbd 2.0 from nbd-2.0.tar.gz) RAID5 (md0) over 3 /dev/nd(x) | | | | | | | | host 4 (node1): | | Kernel 2.4.18 | | nbd-server (nbd 2.0 from nbd-2.0.tar.gz) | | | | | | | host 3 (node1): | Kernel 2.4.18 | nbd-server (nbd 2.0 from nbd-2.0.tar.gz) | host 2 (node0): Kernel 2.4.18 nbd-server (nbd 2.0 from nbd-2.0.tar.gz) Everything seems to be ok, I can startup the nbd-client/server, I can build the RAID5, I can create Filesystem on the md, I can mount, I can Write/Read on it... But, when disconnecting a network link from nbd server (is not relevant if host 2,3 or 4) all process on host 1 in I/O over md0 remain hang in D state for 15 minutes... After this timeout, the host 1 declare the raidset degraded and all is ok again... I have already tried to modify /proc/sys/net/ipv4/tcp_keepalive_xxxxx (thinking the problem to be related to socket or TCP keepalive) but all remain the same: 15 minutes in D state... The same problems on a single block device mounted as simple file system (without RAID). Is there any workaround? Thanks in advance for your help Best Regards Bruno Kropp - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
