public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kay Sievers" <kay.sievers@vrfy.org>
To: "Dave Jones" <davej@redhat.com>,
	"Kay Sievers" <kay.sievers@vrfy.org>,
	"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: film at 11: kernel update breaks udev.
Date: Sat, 21 Jul 2007 03:28:12 +0200	[thread overview]
Message-ID: <3ae72650707201828s22593ef7o7e66ebc2026d36ca@mail.gmail.com> (raw)
In-Reply-To: <20070721011630.GA7017@redhat.com>

On 7/21/07, Dave Jones <davej@redhat.com> wrote:
> On Sat, Jul 21, 2007 at 03:09:55AM +0200, Kay Sievers wrote:
>  > On 7/21/07, Dave Jones <davej@redhat.com> wrote:
>  > > Just one of my machines to 2.6.22.1, and got this during boot..
>  > >
>  > > Starting udev: udevd-event[619]: udev_node_symlink: symlink(../../sdc/dev/disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89) failed: File exists
>  > >
>  > > Under 2.6.21, all was fine.
>  > >
>  > > sdc is one disk of a 3 disk raid5 set.
>  > > The raidset still manages to come up despite this.
>  > >
>  > > This is a Fedora 7 box, with udev-106-4.1.fc7
>  > >
>  > > What changed this time?
>  >
>  > CONFIG_BLK_DEV_BSG=y?
>  >
>  > There's a name-clash, because bsg tries to create devices with the same name.
>  > James sent a patch, it's on lkml.
>
> BSG isn't in 2.6.22

Ok. There has nothing else changed, that I could think of what could cause this.

The code in udev that prints this message looks like:
   err("symlink(%s, %s) failed: %s", linktarget, filename, strerror(errno));

That doesn't really match what you posted. Are there chars missing?
Can you please recheck?

And what does:
  udevtest /block/sdc
print?

Thanks,
Kay

  reply	other threads:[~2007-07-21  1:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-21  1:04 film at 11: kernel update breaks udev Dave Jones
2007-07-21  1:09 ` Kay Sievers
2007-07-21  1:16   ` Dave Jones
2007-07-21  1:28     ` Kay Sievers [this message]
2007-07-21  1:36       ` Dave Jones
2007-07-21  1:55         ` Kay Sievers
2007-07-21  2:20           ` Kay Sievers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3ae72650707201828s22593ef7o7e66ebc2026d36ca@mail.gmail.com \
    --to=kay.sievers@vrfy.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox