Bug#45028: Unable to lock download directory
Jason Gunthorpe said:
> Sounds like you have managed to muck up the NFS mount either by upgrading
> something else recently or by tweaking a kernel bug. Maybe you upgraded
> some of the NFS client/server software?
That's entirely possible, as I let dselect grab the latest versions of all
updated packages. However, a look in the archives cache shows that the
nfs-common package is dated Aug 26 and nfs-server is Aug 20. (Of course,
if apt preserves date stamps on ftp transfers, that doesn't really mean
anything, since I can't remember when I last updated.)
On the other hand, I'd say your basic theory that something screwed NFS up
is likely to be correct, as WindowMaker is now unable to read configurations
for non-root users and, presumably while trying to write those config files,
it segfaults on exit. (/home is also NFS mounted.)
> strace 'apt-get dselect-upgrade' and see why exactly it fails like this.
Here's the last two packages that come up in the strace dump before it dies.
---
read(10, "Package: apple2\nVersion: 0.04-5\n"..., 4855) = 4855
stat("/var/state/apt/lists/ftp.us.debian.org_debian_dists_unstable_main_binary-i386_Packages", {st_mode=S_IFREG|0644, st_size=2568675, ...}) = 0
open("/var/state/apt/lists/ftp.us.debian.org_debian_dists_unstable_main_binary-i386_Packages", O_RDONLY) = 11
fcntl(11, F_SETFD, FD_CLOEXEC) = 0
brk(0x809f000) = 0x809f000
fstat(11, {st_mode=S_IFREG|0644, st_size=2568675, ...}) = 0
read(11, "Package: 2utf\nVersion: 1.10\nPrio"..., 4855) = 4855
open("/var/cache/apt/archives/lock", O_RDWR|O_CREAT|O_TRUNC, 0640) = 12
fcntl(12, F_SETLK, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) = -1 EACCES (Permission denied)
---
Oddly enough, both of these are packages which are neither currently
installed nor marked for install and I'm pretty sure that neither one
has ever been installed on either of my machines.
> I'm betting this is just more Kernel and NFS breakage
Assuming you haven't seen anything here that causes you to change your
mind, any suggestions on how to fix this or who to talk to about it?
Reply to: