Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 164684 - >=sys-fs/udev-103 - broken symlinks in /dev/.udev/db/
Summary: >=sys-fs/udev-103 - broken symlinks in /dev/.udev/db/
Status: RESOLVED OBSOLETE
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High minor (vote)
Assignee: udev maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-31 10:28 UTC by Michael Schreckenbauer
Modified: 2013-03-13 22:29 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Schreckenbauer 2007-01-31 10:28:49 UTC
/dev/.udev/db/ has a lot of dead symlinks like:

lrwxrwxrwx 1 root root   5  1. Jan 05:43 class@tty@ttys4 -> ttys4
lrwxrwxrwx 1 root root   5  1. Jan 05:43 class@tty@ttys5 -> ttys5
lrwxrwxrwx 1 root root   5  1. Jan 05:43 class@tty@ttys6 -> ttys6

Imho those should be:
lrwxrwxrwx 1 root root   5  1. Jan 05:43 class@tty@ttys6 -> ../../ttys6



Reproducible: Always

Steps to Reproduce:
1.Boot machine
2.ls -la /dev/.udev/db/
3.

Actual Results:  
Dead symlinks in /dev/.udev/db

Expected Results:  
Create working symlinks I would say :)

I see this on 3 different systems. All of them are ~x86.
It could be, that this problem exists for much longer time. I never looked into this directory before.

emerge --info for one of them:

portage 2.1.2_rc4-r5 (default-linux/x86/2006.0, gcc-4.1.1, glibc-2.5-r0, 2.6.18-gentoo i686)
=================================================================
System uname: 2.6.18-gentoo i686 Intel(R) Pentium(R) 4 CPU 1.80GHz
Gentoo Base System version 1.12.8
Last Sync: Wed, 03 Jan 2007 09:50:01 +0000
distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
ccache version 2.4 [enabled]
dev-java/java-config: 1.3.7, 2.0.31
dev-lang/python:     2.3.6, 2.4.4
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     2.4-r6
sys-apps/sandbox:    1.2.18.1
sys-devel/autoconf:  2.13, 2.61
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils:  2.17
sys-devel/gcc-config: 1.3.14
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.19
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-march=pentium4 -O2 -fomit-frame-pointer -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/lib/mozilla/defaults/pref /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/splash /etc/terminfo /etc/texmf/web2c"
CXXFLAGS="-march=pentium4 -O2 -fomit-frame-pointer -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache distlocks metadata-transfer parallel-fetch sandbox sfperms strict"
GENTOO_MIRRORS="http://mirror.schlund.de/gentoo/gentoo ftp://ftp.tu-clausthal.de/pub/linux/gentoo/ ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://gentoo.inode.at/source/"
LANG="de_DE@euro"
LINGUAS="de"
MAKEOPTS=""
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.de.gentoo.org/gentoo-portage"
USE="X a52 aac acpi aiglx alsa apache2 apm arts artswrappersuid audiofile bash-completion berkdb bitmap-fonts blender-game bzip2 cairo cddb cdparanoia cli cracklib crypt cscope cups cvs dga directfb dlloader double-precision dri dvd dvdread eds effects emboss encode ffmpeg flac foomaticdb fortran gdbm gif glitz gnome gpm gstreamer gtk gtk2 iconv idn imagemagick imlib ipod ipv6 jabber jack jack-tmpfs java jpeg jpeg2k kde kdeenablefinal lcms ldap libg++ libwww mad matroska mikmod mmx mmxext mng motif mozilla mp3 mpeg musepack mysql ncurses nls nptl nptlonly nsplugin objc offensive ogg openal opengl oracle oss pam pcre pdf perl png pppd python qt3 qt4 quicktime readline real reflection ruby samba sdl session sndfile speex spell spl sse sse2 ssl sysfs tcpd theora tiff truetype truetype-fonts type1-fonts udev usb visualization vorbis win32codecs wmf x86 xcomposite xine xml xorg xscreensaver xv xvid zlib" ALSA_CARDS="intel8x0" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LINGUAS="de" USERLAND="GNU" VIDEO_CARDS="nvidia"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS

udev-Version is 103 on this system, my colleague has udev-104-r5 which creates dead links there too.

We have no real problem at all. The systems are all working like a charm.
Maybe this dir is not needed? ;)
Comment 1 Matthias Schwarzott gentoo-dev 2007-01-31 10:47:41 UTC
Hmm, my udev does not create links in /dev/.udev/db/. All entries there are files.
Perhaps you use RC_DEVICE_TARBALL?

RC_DEVICE_TARBALL does safe all device-nodes and symlinks from /dev. Before version udev-104-r3, it also stored the links it found in /dev/.udev/db/.

That mean they should not be stored at next shutdown and not reappear.
Comment 2 Michael Schreckenbauer 2007-01-31 11:52:52 UTC
(In reply to comment #1)
> Hmm, my udev does not create links in /dev/.udev/db/. All entries there are
> files.
> Perhaps you use RC_DEVICE_TARBALL?

Sorry, no. RC_DEVICE_TARBALL is set to "no" on our machines.

Here is, what it looks like for me:
/dev/.udev/db $ find . -type l|wc -l
627
/dev/.udev/db $ find . -type f|wc -l
50

All of the links are broken.

Thanks for the amazingly fast response :)

Comment 3 Matthias Schwarzott gentoo-dev 2007-01-31 12:47:49 UTC
Other solution:
Did you already boot with newest udev-version, or updated while system was already running.

And please check the content of /lib/udev/state/ and /lib/udev/devices/
Comment 4 Jakub Moc (RETIRED) gentoo-dev 2007-01-31 15:21:27 UTC
Here's an idea... Go reboot :) No dead symlinks after that (see previous comment).
Comment 5 Michael Schreckenbauer 2007-01-31 15:51:33 UTC
(In reply to comment #4)
> Here's an idea... Go reboot :) No dead symlinks after that (see previous
> comment).

The first thing I tried actually. No, that didn't work.
What a strange suggestion by the way. Since when is this necessary using Linux?
It's udev, not a new kernel ;)

Requested dirs are:

$ ls -la /lib/udev/state/
insgesamt 29
drwxr-xr-x 2 root root   120 25. Okt 17:05 .
drwxr-xr-x 4 root root   568 25. Okt 17:05 ..
-rw-r--r-- 1 root root 26718 25. Okt 17:05 devices.tar.bz2
-rw-r--r-- 1 root root     0 25. Okt 17:05 .keep_sys-fs_udev-0

I have a tarball here. But my colleagues don't. No idea why it is there...

$ ls -la /lib/udev/devices/
insgesamt 1
drwxr-xr-x 2 root root  144 26. Sep 18:09 .
drwxr-xr-x 4 root root  568 25. Okt 17:05 ..
crw------- 1 root tty  5, 1 22. Okt 2000  console
crw-rw-rw- 1 root root 1, 3 22. Okt 2000  null
crw-rw-rw- 1 root root 1, 9 22. Okt 2000  urandom
crw-rw-rw- 1 root root 1, 5 22. Okt 2000  zero

I am now told, that one of us had success with the reboot, so your suggestion was a good one :)
Does it make sense to delete the contents manually or is this somehow dangerous for my systems? Maybe these are leftovers, this machine was installed 3,5 years ago.

Thanks very much,
Michael
Comment 6 Michael Schreckenbauer 2007-02-01 19:27:19 UTC
After deleting the links manually and rebooting, the links got recreated.
This happens on the udev-103 machines. The udev-104(-r5 iirc) machine got fixed by the reboot.
Situation now is:
2x udev-103: dead symlinks, reboot does not solve anything
udev-104: solved
I am now updating my PC to udev-104.

Uh, I now see, the dead links I posted here are quite old. Do you believe me the situation is the same or should I post newer ones (eg today)? ;)

Thanks,
Michael

BTW: what's policy here? Should I reopen the bug?