On 2021-01-23 09:38:52 +0100, steve wrote:
> ❯ stat /dev/sdc6
> Fichier : /dev/sdc6
>Taille : 0 Blocs : 0 Blocs d'E/S : 4096 fichier
> spécial de blocs
> Périphérique : 5h/5dInœud : 266 Liens : 1 Type de périph. :
> 8,26
> Accès : (0660/brw-rw) UID
Le 22-01-2021, à 13:21:53 -0600, David Wright a écrit :
On Fri 22 Jan 2021 at 08:06:37 (+0100), steve wrote:
Le 21-01-2021, à 20:41:05 -0600, David Wright a écrit :
> I always archive the output of udevadm for my disks (actually
> I just copy the /run/udev/data/b8\:* files).
I don't understan
Le 22-01-2021, à 13:40:20 +0100, Vincent Lefevre a écrit :
> Could you inspect the /dev directory from a live image or similar (i.e.
> with the affected system not running)?
Yes I can do that. What should I look for?
As usual, the error message gives the name of the symlink: sdc6,
so that sho
Le 22-01-2021, à 14:59:27 +0200, Andrei POPESCU a écrit :
On Vi, 22 ian 21, 08:08:57, steve wrote:
Le 21-01-2021, à 09:45:18 +0200, Andrei POPESCU a écrit :
> On Jo, 21 ian 21, 08:34:34, steve wrote:
> > I have rebooted with udev_log=debug in /etc/udev/udev.conf. I see
> >
> > Jan 21 08:15:28
David Wright wrote:
>
> > > Does mdadm have a
> > > equivalent manner of displaying its configuration?
>
> Not having used it, I wondered whether mdadm could effortlessly
> "brain-dump" in a similar manner to either of these methods.
sudo mdadm --detail --scan
will produce all the necessary in
On Fri 22 Jan 2021 at 08:06:37 (+0100), steve wrote:
> Le 21-01-2021, à 20:41:05 -0600, David Wright a écrit :
>
> > I always archive the output of udevadm for my disks (actually
> > I just copy the /run/udev/data/b8\:* files).
>
> I don't understand.
I keep a log for each of my hard drives, its
On Vi, 22 ian 21, 08:08:57, steve wrote:
> Le 21-01-2021, à 09:45:18 +0200, Andrei POPESCU a écrit :
>
> > On Jo, 21 ian 21, 08:34:34, steve wrote:
> > > I have rebooted with udev_log=debug in /etc/udev/udev.conf. I see
> > >
> > > Jan 21 08:15:28 box systemd-udevd[607]: sdc6: Failed to update de
On 2021-01-22 08:08:57 +0100, steve wrote:
> Le 21-01-2021, à 09:45:18 +0200, Andrei POPESCU a écrit :
>
> > On Jo, 21 ian 21, 08:34:34, steve wrote:
> > > I have rebooted with udev_log=debug in /etc/udev/udev.conf. I see
> > >
> > > Jan 21 08:15:28 box systemd-udevd[607]: sdc6: Failed to update
Le 21-01-2021, à 09:45:18 +0200, Andrei POPESCU a écrit :
On Jo, 21 ian 21, 08:34:34, steve wrote:
I have rebooted with udev_log=debug in /etc/udev/udev.conf. I see
Jan 21 08:15:28 box systemd-udevd[607]: sdc6: Failed to update device symlinks:
Too many levels of symbolic links
Jan 21 08:15:2
Hi,
Le 21-01-2021, à 20:41:05 -0600, David Wright a écrit :
On Thu 21 Jan 2021 at 08:34:34 (+0100), steve wrote:
I have rebooted with udev_log=debug in /etc/udev/udev.conf. I see
Jan 21 08:15:28 box systemd-udevd[607]: sdc6: Failed to update device symlinks:
Too many levels of symbolic links
On Thu 21 Jan 2021 at 08:34:34 (+0100), steve wrote:
> I have rebooted with udev_log=debug in /etc/udev/udev.conf. I see
>
> Jan 21 08:15:28 box systemd-udevd[607]: sdc6: Failed to update device
> symlinks: Too many levels of symbolic links
> Jan 21 08:15:28 box systemd-udevd[607]: sdc6: Preserve
On Jo, 21 ian 21, 08:34:34, steve wrote:
> I have rebooted with udev_log=debug in /etc/udev/udev.conf. I see
>
> Jan 21 08:15:28 box systemd-udevd[607]: sdc6: Failed to update device
> symlinks: Too many levels of symbolic links
> Jan 21 08:15:28 box systemd-udevd[607]: sdc6: Preserve already exi
I have rebooted with udev_log=debug in /etc/udev/udev.conf. I see
Jan 21 08:15:28 box systemd-udevd[607]: sdc6: Failed to update device symlinks:
Too many levels of symbolic links
Jan 21 08:15:28 box systemd-udevd[607]: sdc6: Preserve already existing symlink
'/dev/disk/by-path/pci-:00:17.0
Le 20-01-2021, à 16:06:53 -0500, Stefan Monnier a écrit :
Le 20-01-2021, à 10:15:47 -0500, Stefan Monnier a écrit :
# find /dev -follow -printf ""
You want `-mount` in there so you don't enter things like `/dev/fd` or
`/dev/shm`.
I tried that on /
Not a good idea: the `-mount` will then pre
> Le 20-01-2021, à 10:15:47 -0500, Stefan Monnier a écrit :
>>> # find /dev -follow -printf ""
>>You want `-mount` in there so you don't enter things like `/dev/fd` or
>>`/dev/shm`.
> I tried that on /
Not a good idea: the `-mount` will then preventing it from entering
`/dev` since `/dev` is usual
Le 20-01-2021, à 10:15:47 -0500, Stefan Monnier a écrit :
# find /dev -follow -printf ""
You want `-mount` in there so you don't enter things like `/dev/fd` or
`/dev/shm`.
I tried that on / and got no output at all.
But still have the same messages in syslog at boot time.
Thanks.
> # find /dev -follow -printf ""
You want `-mount` in there so you don't enter things like `/dev/fd` or
`/dev/shm`.
Stefan
Le 20-01-2021, à 11:30:50 +0100, Erwan David a écrit :
What is strange is that it is always /dev/fd/4 that is missing, even
after a reboot.
it is not missing : it disapears. And /dev/fd/4 is a link to a file
opend by find itself, it is sufficient that find closes it and the
name does not e
On Wed, Jan 20, 2021 at 11:30:50AM +0100, Erwan David wrote:
[...]
> it is not missing : it disapears. And /dev/fd/4 is a link to a file
> opend by find itself, it is sufficient that find closes it and the
> name does not exist anymore.
Thanks for putting this in a less roundabout way than I did
Le 20/01/2021 à 10:49, steve a écrit :
Thanks Mike and Thomas for the answers.
Le 20-01-2021, à 10:15:09 +0100, to...@tuxteam.de a écrit :
On Wed, Jan 20, 2021 at 09:40:46AM +0100, steve wrote:
Question. What does the following mean?
# find /dev -follow -printf ""
find: '/dev/fd/4': No such
Le 20-01-2021, à 11:20:25 +0100, to...@tuxteam.de a écrit :
The /proc file system is pretty interesting indeed. But I don't think
that is at the root of your strange problem.
...
My current is to find out why my system is spitting out these 'too many
symnolic links' messages and then fix it
On Wed, Jan 20, 2021 at 11:15:26AM +0100, steve wrote:
> Le 20-01-2021, à 10:58:54 +0100, to...@tuxteam.de a écrit :
>
> # find /dev -follow -printf ""
[...]
> >This process in this case is the one running `find' itself. At the
[...]
> Ah ok, I misunderstood that. Very interesting indeed.
Le 20-01-2021, à 10:58:54 +0100, to...@tuxteam.de a écrit :
>># find /dev -follow -printf ""
>>find: '/dev/fd/4': No such file or directory
>
>This is funny. At first I thought I could reproduce it by tricking `find'
>into following a broken symlink, but with a "static" setup I couldn't.
>
>Stil
On Wed, Jan 20, 2021 at 10:49:08AM +0100, steve wrote:
> Thanks Mike and Thomas for the answers.
>
> Le 20-01-2021, à 10:15:09 +0100, to...@tuxteam.de a écrit :
>
> >On Wed, Jan 20, 2021 at 09:40:46AM +0100, steve wrote:
> >>Question. What does the following mean?
> >>
> >># find /dev -follow -pr
Thanks Mike and Thomas for the answers.
Le 20-01-2021, à 10:15:09 +0100, to...@tuxteam.de a écrit :
On Wed, Jan 20, 2021 at 09:40:46AM +0100, steve wrote:
Question. What does the following mean?
# find /dev -follow -printf ""
find: '/dev/fd/4': No such file or directory
This is funny. At fi
On Wed, Jan 20, 2021 at 09:40:46AM +0100, steve wrote:
> Question. What does the following mean?
>
> # find /dev -follow -printf ""
> find: '/dev/fd/4': No such file or directory
This is funny. At first I thought I could reproduce it by tricking `find'
into following a broken symlink, but with a
On 2021-01-20 08:40, steve wrote:
Question. What does the following mean?
# find /dev -follow -printf ""
find: '/dev/fd/4': No such file or directory
I don't know but they look to be symlinks that get created to pseudo
terminals /dev/pts/0 by eg ssh, telnet.
Maybe a session crashed and left
Question. What does the following mean?
# find /dev -follow -printf ""
find: '/dev/fd/4': No such file or directory
Oups, spoke too quickly.
I decreased udev log level, rebooted and the messages came back in
syslog.
Hi,
I deleted some symlinks found in my home, updated the system (bullseye)
this morning, increased udev log level to debug and rebooted the system.
grep symlinks /var/log/syslog
didn't show any mention of previous problem.
Le 19-01-2021, à 11:01:24 -0600, David Wright a écrit :
On Tue 19
On Tue 19 Jan 2021 at 11:15:05 (-0500), Greg Wooledge wrote:
> On Tue, Jan 19, 2021 at 04:03:14PM +0100, steve wrote:
> > > It'd be interesting to know which one your startup is choking on.
> >
> > What does it mean more precisely? The lines come from syslog and only
> > mention partitions:
> >
>
Le 19-01-2021, à 17:11:58 +0100, to...@tuxteam.de a écrit :
>It'd be interesting to know which one your startup is choking on.
What does it mean more precisely? The lines come from syslog and only
mention partitions:
Jan 19 09:09:33 box systemd-udevd[607]: sdg6: Failed to update device symlink
On Tue, Jan 19, 2021 at 04:03:14PM +0100, steve wrote:
> > It'd be interesting to know which one your startup is choking on.
>
> What does it mean more precisely? The lines come from syslog and only
> mention partitions:
>
> Jan 19 09:09:33 box systemd-udevd[607]: sdg6: Failed to update device
>
On Tue, Jan 19, 2021 at 04:03:14PM +0100, steve wrote:
> Le 19-01-2021, à 15:53:00 +0100, to...@tuxteam.de a écrit :
>
> >>find /usr -follow -printf ""
> >>find: Boucle détectée dans le système de fichiers ; « ‘/usr/bin/X11’ » est
> >>dans la même boucle que ‘/usr/bin’.
> >>
> >>ls -l /usr/bin/X1
Le 19-01-2021, à 15:53:00 +0100, to...@tuxteam.de a écrit :
find /usr -follow -printf ""
find: Boucle détectée dans le système de fichiers ; « ‘/usr/bin/X11’ » est dans
la même boucle que ‘/usr/bin’.
ls -l /usr/bin/X11
lrwxrwxrwx 1 root root 1 6 mai 2013 /usr/bin/X11 -> .
find /sys -follow
On Tue, Jan 19, 2021 at 03:45:41PM +0100, steve wrote:
> Le 19-01-2021, à 14:49:36 +0100, to...@tuxteam.de a écrit :
>
> >On Tue, Jan 19, 2021 at 07:41:13AM -0500, Greg Wooledge wrote:
> >>On Tue, Jan 19, 2021 at 10:03:12AM +0100, steve wrote:
> >>> Jan 19 09:47:52 box systemd-udevd[611]: sdg5: Fa
Le 19-01-2021, à 14:49:36 +0100, to...@tuxteam.de a écrit :
On Tue, Jan 19, 2021 at 07:41:13AM -0500, Greg Wooledge wrote:
On Tue, Jan 19, 2021 at 10:03:12AM +0100, steve wrote:
> Jan 19 09:47:52 box systemd-udevd[611]: sdg5: Failed to update device
symlinks: Too many levels of symbolic links
On Tue, Jan 19, 2021 at 07:41:13AM -0500, Greg Wooledge wrote:
> On Tue, Jan 19, 2021 at 10:03:12AM +0100, steve wrote:
> > Jan 19 09:47:52 box systemd-udevd[611]: sdg5: Failed to update device
> > symlinks: Too many levels of symbolic links
> > Jan 19 09:47:52 box systemd-udevd[581]: sdg6: Failed
On Tue, Jan 19, 2021 at 10:03:12AM +0100, steve wrote:
> Jan 19 09:47:52 box systemd-udevd[611]: sdg5: Failed to update device
> symlinks: Too many levels of symbolic links
> Jan 19 09:47:52 box systemd-udevd[581]: sdg6: Failed to update device
> symlinks: Too many levels of symbolic links
Look
On Saturday 03 September 2005 01:10 am, Gudjon I. Gudjonsson wrote:
> Hi
>I have tried for some time to compile modules with module-assistant.
> Both alsa and nvidia fail with the comment: Too many levels of symbolic
> links. Similar description to the following message.
> http://lists.debian.o
Just curious,
is kernel-source-2.6.12-1 available somewhere ?
Thanks,
Jerome
Steven Noble wrote:
Just dealt with the same problem. For some reason purging the header
packages, deleting the archived copies, and then reinstalling them fixes
the problem. At least it did for me.
Steven
On 9/3
Just dealt with the same problem. For some reason purging the
header packages, deleting the archived copies, and then reinstalling
them fixes the problem. At least it did for me.
StevenOn 9/3/05, Gudjon I. Gudjonsson <[EMAIL PROTECTED]> wrote:
Hi I have tried for some time to compile modules w
42 matches
Mail list logo
