lmi
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lmi] Crashed debian while installing centos chroot


From: Greg Chicares
Subject: [lmi] Crashed debian while installing centos chroot
Date: Wed, 2 Oct 2019 16:26:11 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0

Vadim--I post this in case you have any insight to share.

Debian (stable) crashed while I was running a script (which I have
not yet committed):
  install_centos.sh >centos_log_20191002T1539Z 2>&1
I don't know exactly what happened, because I was doing that in
/tmp, whence the log got purged when I finally managed to reboot.

[I had enabled already enabled SysReq magic:
  echo "kernel.sysrq = 1" >> /etc/sysctl.d/local.conf
and REISU worked, but not B. Apparently LeftAlt-SysReq works
better than RightAlt-SysReq. But I eventually got B to work
by holding and releasing the relevant keys repeatedly.]

Now I've tried installing centos again, and the log says
(during "+ rinse --arch amd64...",
and after "Execute postcmd of *-release package"):

$grep lock centos_log_20191002T1539Z 
mv: inter-device move failed: '/srv/chroot/centos7/var/run/lock' to 
'/srv/chroot/centos7/run/lock'; unable to remove target: Directory not empty
ln: failed to create symbolic link '/srv/chroot/centos7/var/lock/lock': File 
exists

Poking around, I see:

$ls -l /srv/chroot/centos7/var/lock/lock
lrwxrwxrwx 1 root root 9 Oct  2 15:29 /srv/chroot/centos7/var/lock/lock -> 
/run/lock

$ls -l /run/lock/lock/lock 
lrwxrwxrwx 1 root root 9 Oct  2 15:29 /run/lock/lock/lock -> /run/lock

Isn't that circular? Anyway, I seem to be okay:

#lslocks
COMMAND   PID  TYPE SIZE MODE  M START END PATH
cron      993 FLOCK   4B WRITE 0     0   0 /run/crond.pid (deleted)

so I guess I'll delete that chroot and try again.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]