[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3ae72650707201828s22593ef7o7e66ebc2026d36ca@mail.gmail.com>
Date: Sat, 21 Jul 2007 03:28:12 +0200
From: "Kay Sievers" <kay.sievers@...y.org>
To: "Dave Jones" <davej@...hat.com>,
"Kay Sievers" <kay.sievers@...y.org>,
"Linux Kernel" <linux-kernel@...r.kernel.org>
Subject: Re: film at 11: kernel update breaks udev.
On 7/21/07, Dave Jones <davej@...hat.com> wrote:
> On Sat, Jul 21, 2007 at 03:09:55AM +0200, Kay Sievers wrote:
> > On 7/21/07, Dave Jones <davej@...hat.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists