From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S939918AbXGUB2X (ORCPT ); Fri, 20 Jul 2007 21:28:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756534AbXGUB2O (ORCPT ); Fri, 20 Jul 2007 21:28:14 -0400 Received: from nz-out-0506.google.com ([64.233.162.224]:2864 "EHLO nz-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757923AbXGUB2N (ORCPT ); Fri, 20 Jul 2007 21:28:13 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=WxbEU3oyxYxnCOy3kDp7xS64dkawqlAUdDVPVzvCzdEmMP6Cl9GIfXh7OH16FqQ6eIc60u74sX1H/DOoBsEIGopsHgyONvhw1B636kMvfFQNkN1W0HIHv/5Dmy1zEUbaFLHX5WwPkQIac7+gLlQpbBQLkK8N2rnLVig+KBa57Gg= Message-ID: <3ae72650707201828s22593ef7o7e66ebc2026d36ca@mail.gmail.com> Date: Sat, 21 Jul 2007 03:28:12 +0200 From: "Kay Sievers" To: "Dave Jones" , "Kay Sievers" , "Linux Kernel" Subject: Re: film at 11: kernel update breaks udev. In-Reply-To: <20070721011630.GA7017@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070721010424.GA4411@redhat.com> <3ae72650707201809l33019f56i202c1a1ddd61007f@mail.gmail.com> <20070721011630.GA7017@redhat.com> X-Google-Sender-Auth: 8429a1303f5cc895 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 7/21/07, Dave Jones wrote: > On Sat, Jul 21, 2007 at 03:09:55AM +0200, Kay Sievers wrote: > > On 7/21/07, Dave Jones 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