Bug#193883: cannot remove directory `/tmp/dpkg7rZQXe
Guillem Jover writes: > Right, but I was suggesting trying with lookupcache=none,noac or > combinations of those. I did that now but also realized that /tmp is nowadays on a tmpfs :-) Anyways, I'll let you know if I ever hit the bug again. -Timo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#193883: cannot remove directory `/tmp/dpkg7rZQXe
Hi, Guillem Jover writes: > Definitely not dpkg fault, as it fails on “rm -rf”, and given this > appear to be not a Debian kernel, I think I'll be closing in short > time. I'm not sure we can do much here. That's ok. I'm now mostly using Debian kernels in such diskless setups and have not hit this bug recently (however, I am using apt-get a lot more than aptitude nowadays anyway). >> $ cat /proc/mounts >> /dev/root / nfs >> rw,vers=2,rsize=4096,wsize=4096,hard,nolock,proto=udp,timeo=11,retrans=2,addr=130.233.244.172 >> 0 0 >> nfs:/home /home nfs >> rw,vers=3,rsize=8192,wsize=8192,hard,proto=udp,timeo=7,retrans=3,addr=nfs 0 0 > > Anyway in case you have such setup still available, could you play > with the nfs caching mount options, at least lookupcache and noac? aptitude seems to generally work in my setup with 10.7.2.17:/tftpboot/garfield / nfs rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,hard,nolock,proto=tcp,port=65535,timeo=7,retrans=10,sec=sys,mountport=65535,addr=10.7.2.17 0 0 and linux-image-2.6.32-5-4862.6.32-31 If I read "man nfs" correctly then the default is already lookupcache=all,ac? -Timo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#193883: cannot remove directory `/tmp/dpkg7rZQXe
Hi! On Tue, 2006-10-31 at 00:17:21 +0200, Timo Juhani Lindfors wrote: > The bug definitely still exists but it's probably not dpkg's fault. I > don't know where you should reassing this either... Definitely not dpkg fault, as it fails on “rm -rf”, and given this appear to be not a Debian kernel, I think I'll be closing in short time. I'm not sure we can do much here. > The bug occurs with a custom linux 2.6.17 kernel, I unfortunately > can't test this with a kernel from debian. > > $ cat /proc/mounts > /dev/root / nfs > rw,vers=2,rsize=4096,wsize=4096,hard,nolock,proto=udp,timeo=11,retrans=2,addr=130.233.244.172 > 0 0 > nfs:/home /home nfs > rw,vers=3,rsize=8192,wsize=8192,hard,proto=udp,timeo=7,retrans=3,addr=nfs 0 0 Anyway in case you have such setup still available, could you play with the nfs caching mount options, at least lookupcache and noac? thanks, guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org