Hi,
I've been doing some work with nbd-servers, but it seems they are
a bit unreliable right now. It seems to be the kernel side that
is locking up.
Doing things like
dd if=/dev/zero of=filesys bs=1k count=1 seek=1024000
nbd-server 1234 `pwd`/filesys
and then
nbd-client othersystem 1234
Hi,
I've been doing some work with nbd-servers, but it seems they are
a bit unreliable right now. It seems to be the kernel side that
is locking up.
Doing things like
dd if=/dev/zero of=filesys bs=1k count=1 seek=1024000
nbd-server 1234 `pwd`/filesys
and then
nbd-client othersystem 1234
Hi!
> I've been having some NBD hangs with the 2.4.2 kernel. It appears that
> block devices which don't use plugging will not have their request
> functions called when the request is queued. I propose the following
> patch to ll_rw_blk.c which seems to do the trick for me. Also I
Hi,
I've been having some NBD hangs with the 2.4.2 kernel. It appears that
block devices which don't use plugging will not have their request
functions called when the request is queued. I propose the following
patch to ll_rw_blk.c which seems to do the trick for me. Also I have
done a small
Hi,
I've been having some NBD hangs with the 2.4.2 kernel. It appears that
block devices which don't use plugging will not have their request
functions called when the request is queued. I propose the following
patch to ll_rw_blk.c which seems to do the trick for me. Also I have
done a small
Hi!
I've been having some NBD hangs with the 2.4.2 kernel. It appears that
block devices which don't use plugging will not have their request
functions called when the request is queued. I propose the following
patch to ll_rw_blk.c which seems to do the trick for me. Also I have
done
6 matches
Mail list logo