| Summary: | >=sys-fs/udev-103 - broken symlinks in /dev/.udev/db/ | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Michael Schreckenbauer <grimlog> |
| Component: | [OLD] Core system | Assignee: | udev maintainers <udev-bugs> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | minor | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Michael Schreckenbauer
2007-01-31 10:28:49 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. (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 :) 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/ Here's an idea... Go reboot :) No dead symlinks after that (see previous comment). (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 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? |
