Re: film at 11: kernel update breaks udev.

On 7/21/07, Dave Jones <[email protected]> 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.

Kay
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: film at 11: kernel update breaks udev.
    • From: Dave Jones <[email protected]>

• References:
  • film at 11: kernel update breaks udev.
    • From: Dave Jones <[email protected]>

• Prev by Date: Re: [PATCH] hugetlbfs read() support
• Next by Date: Re: where is the code for read system call?
• Previous by thread: film at 11: kernel update breaks udev.
• Next by thread: Re: film at 11: kernel update breaks udev.
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]