Bug#627500: Bug#627509: Bug#627500: udev 169-1 configuration fail

2011-05-30 Thread Marco d'Itri
On May 29, Lucas Le Dore lucasled...@gmail.com wrote:

 The problem on 2) is that udevd keeps /run directory busy (managing
Good catch. The problem actually is that udevd should not be running
anymore at that point, I need to understand better why it is not being
killed.

-- 
ciao,
Marco


signature.asc
Description: Digital signature


Bug#627500: udev 169-1 configuration fail

2011-05-29 Thread Lucas Le Dore
On Fri, May 27, 2011 at 5:07 PM, Marco d'Itri m...@linux.it wrote:
 Curious thing is that even if the directory does not exist,
 /proc/mounts displays it as mounted...
 I would say impossibile, even.

Is it ?

However, it's the state after bootup with udev-168.2 and
initscripts-2.88dsf-13.2, if the /run directory is not present on
rootfs.

If rootfs does not contain /run, default behavior of initramfs init script is:
1) Move /run/udev and /run/initramfs to /dev/.udev and /dev/.initramfs
2) Umount /run

The problem on 2) is that udevd keeps /run directory busy (managing
/run/udev/queue.bin, even deleted); it can't be unmounted. After
chroot, /proc/mounts still displays /run, which is not present on the
rootfs.

Note that the latest initscripts does not even let the system boot if
the /run directory is not here.

Now I have to figure when and what process should normally have
created that directory on my system, and why it didn't.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#627500: udev 169-1 configuration fail

2011-05-29 Thread Marco Menardi

I've had the same issue!
Hope that the following info will help.

The installation failed:
Setting up udev (170-1) ...
mv: cannot move `/dev/.udev/' to `/run/udev/': No such file or directory
dpkg: error processing udev (--configure):
 subprocess installed post-installation script returned error exit status 1
configured to not write apport reports

(and so did all the rest of the full-upgrade).
Then I found this bug and tested this:

thor:~# cat /proc/mounts | grep run
tmpfs /run tmpfs rw,nosuid,relatime,size=812300k,mode=755 0 0
thor:~#

thor:~# ls -l /
totale 127
drwxr-xr-x   2 root  root   4096 29 mag 11.17 bin
drwxr-xr-x   6 root  root   3072 29 mag 11.27 boot
lrwxrwxrwx   1 root  root 11 13 mag  2007 cdrom - media/cdrom
drwxr-xr-x  18 root  root   3540 29 mag 10.59 dev
drwxr-xr-x   3 root  root   4096 13 mag  2007 emul
drwxr-xr-x 181 root  root  12288 29 mag 11.36 etc
drwxrwsr-x   7 root  staff  4096 28 mag  2010 home
drwxr-xr-x   2 root  root   4096 13 mag  2007 initrd
lrwxrwxrwx   1 root  root 31 26 mag 20.35 initrd.img - 
/boot/initrd.img-2.6.39-1-amd64
lrwxrwxrwx   1 root  root 30 19 mar 14.10 initrd.img.old - 
boot/initrd.img-2.6.38-1-amd64

drwxr-xr-x  16 root  root  16384 29 mag 11.22 lib
drwxr-xr-x   4 root  root  12288 12 mag 23.09 lib32
lrwxrwxrwx   1 root  root  4 15 set  2007 lib64 - /lib
drwx--   2 root  root  16384 22 gen  2010 lost+found
drwxr-xr-x   5 root  root   4096 29 mag 10.59 media
drwxr-xr-x  12 root  root   4096 31 mar 22.07 mnt
drwxr-xr-x   6 marco users  4096 27 feb 16.41 opt
dr-xr-xr-x 132 root  root  0 29 mag  2011 proc
drwxr-xr-x  45 root  root   4096 28 mag 16.47 root
drwxr-xr-x   2 root  root  12288 29 mag 11.18 sbin
drwxr-xr-x   2 root  root   4096  8 mar  2007 selinux
drwxr-xr-x  25 marco root   4096  4 mag 23.03 srv
drwxr-xr-x  13 root  root  0 29 mag  2011 sys
drwxrwxrwx  21 root  root   4096 29 mag 11.41 tmp
drwxr-xr-x  13 root  root   4096  1 ott  2010 usr
drwxr-xr-x  14 root  root   4096 18 lug  2010 var
lrwxrwxrwx   1 root  root 27 26 mag 20.35 vmlinuz - 
boot/vmlinuz-2.6.39-1-amd64
lrwxrwxrwx   1 root  root 27 19 mar 14.10 vmlinuz.old - 
boot/vmlinuz-2.6.38-1-amd64

thor:~#


Then I did:
# mkdir /run
and
# aptitude full-upgrade
again.
This time everything went fine, fortunatly!
Best regards
Marco Menardi



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#627500: udev 169-1 configuration fail

2011-05-27 Thread Lucas Le Doré
Sorry for the delay.

I don't know on which stage the /run directory should have been
created, but I had to do it myself to make things work.
Curious thing is that even if the directory does not exist,
/proc/mounts displays it as mounted...


Thanks,
Lucas



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#627500: udev 169-1 configuration fail

2011-05-27 Thread Marco d'Itri
On May 27, Lucas Le Doré lucasled...@gmail.com wrote:

 Curious thing is that even if the directory does not exist,
 /proc/mounts displays it as mounted...
I would say impossibile, even.

-- 
ciao,
Marco


signature.asc
Description: Digital signature


Bug#627500: udev 169-1 configuration fail

2011-05-24 Thread Marco d'Itri
severity 627500 normal
tag 627500 unreproducible moreinfo
thanks

I am unable to reproduce this bug and the submitter did not provide any
useful information, so I am demoting it.

-- 
ciao,
Marco


signature.asc
Description: Digital signature


Bug#627500: udev 169-1 configuration fail

2011-05-21 Thread Lucas LE DORE
Package: udev
Version: 169-1
Severity: grave

aptitude upgrade fail on udev 169-1 configuration:

Setting up udev (169-1) ...
mv: cannot move `/dev/.udev/' to `/run/udev/': No such file or directory
dpkg: error processing udev (--configure):
 subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
  dpkg: dependency problems prevent 
configuration of fuse-utils:
 fuse-utils depends on udev | makedev (= 2.3.1-80); however:
  Package udev is not configured yet.
  Package makedev is not installed.


Dependant and subsequent packages could not be updated.



-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.38-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages udev depends on:
ii  debconf [debconf-2.0]1.5.39  Debian configuration management sy
ii  libc62.13-4  Embedded GNU C Library: Shared lib
ii  libselinux1  2.0.98-1+b1 SELinux runtime shared libraries
ii  libudev0 169-1   libudev shared library
ii  lsb-base 3.2-27  Linux Standard Base 3.2 init scrip
ii  util-linux   2.17.2-9.1  Miscellaneous system utilities

Versions of packages udev recommends:
ii  pciutils  1:3.1.7-9  Linux PCI Utilities
ii  usbutils  1:001-1Linux USB utilities

udev suggests no packages.

-- Configuration Files:
/etc/modprobe.d/blacklist.conf changed [not included]

-- debconf information:
  udev/new_kernel_needed: false
  udev/title/upgrade:
  udev/reboot_needed:
  udev/sysfs_deprecated_incompatibility:



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#627500: udev 169-1 configuration fail

2011-05-21 Thread Marco d'Itri
 mv: cannot move `/dev/.udev/' to `/run/udev/': No such file or directory
I do not understand how this could happen since postinst checks that
/run is mounted. How is your system different?

  if ! chrooted  [ -d /dev/.udev/ -a ! -d /run/udev/ ] \
   grep -E -q ^[^[:space:]]+ /run tmpfs  /proc/mounts; then
mv /dev/.udev/ /run/udev/
  fi

-- 
ciao,
Marco


signature.asc
Description: Digital signature


Bug#627500: udev 169-1 configuration fail

2011-05-21 Thread Alexander Heinlein
On Sat, May 21, 2011 at 05:00:00PM +0200, Marco d'Itri wrote:
  mv: cannot move `/dev/.udev/' to `/run/udev/': No such file or directory
 I do not understand how this could happen since postinst checks that
 /run is mounted. How is your system different?
 

I don't know, nothing special here. If it helps, trying to install the
package a second time succeeded. Now I've got also the /run directory filled
with lots of files and directories :).

Regards,
Alex



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org