Bug#605472: sysfs: cannot create duplicate filename
Gregory Auzanneau wrote:
> I just finish a fresh install of debian squeeze with debian-test1 CD
> and after boot I get several Warning :
> scsi 0:2:0:0: Direct-Access LSI RAID 5/6 SAS 6G 2.40 PQ: 0 ANSI: 5
> sd 0:2:0:0: [sda] 4677218560 512-byte logical blocks: (2.39 TB/2.17 TiB)
> sd 0:2:0:0: [sda] Write Protect is off
> sd 0:2:0:0: [sda] Mode Sense: 1f 00 00 08
> sd 0:2:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> ------------[ cut here ]------------
> WARNING: at [...]/fs/sysfs/dir.c:491 sysfs_add_one+0xcc/0xe4()
> Hardware name: PRIMERGY RX300 S6
> sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:0:16/0:0:16:0/enclosure/0:0:16:0/ArrayDevice03'
> Modules linked in: sd_mod ses(+) crc_t10dif enclosure uhci_hcd(+) ahci(+) mptsas(+) mptscsih libata megaraid_sas igb(+) mptbase scsi_transport_sas ehci_hcd dca thermal usbcore nls_base scsi_mod thermal_sys
> Pid: 382, comm: modprobe Not tainted 2.6.32-5-amd64 #1
> Call Trace:
> [<ffffffff8118f3f3>] ? kobject_add+0x74/0x7c
> [<ffffffff810e7b3d>] ? __kmalloc+0x12f/0x141
> [<ffffffff8121dc20>] ? device_private_init+0x13/0x45
> [<ffffffff8121e0c2>] ? device_add+0xce/0x537
> [<ffffffffa00374d1>] ? enclosure_component_register+0xbe/0xf9 [enclosure]
> [<ffffffffa007d594>] ? ses_enclosure_data_process+0x18b/0x2a1 [ses]
> [<ffffffffa007db1b>] ? ses_intf_add+0x331/0x439 [ses]
> [<ffffffff81220b84>] ? class_interface_register+0x94/0xcf
> [<ffffffffa008b000>] ? ses_init+0x0/0x35 [ses]
> [<ffffffffa008b00d>] ? ses_init+0xd/0x35 [ses]
> [<ffffffff8100a065>] ? do_one_initcall+0x64/0x174
> [<ffffffff8107a594>] ? sys_init_module+0xc5/0x21a
> [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b
> ---[ end trace 2204c34c56d00ffd ]---
> kobject_add_internal failed for ArrayDevice03 with -EEXIST, don't try to register things with the same name in the same directory.
> Thank you all for the good work, keep up with it !
Do you still have access to this machine, and if so, were you able to
get it to boot somehow?
The device name seems to come from page 7, which gives "pretty" names
to enclosure slots. Unfortunately, it looks like multiple slots have
the same name here.
Two possible bugs:
- maybe the kernel's confused, and multiple slots did not actually
have the same name;
- even if it is the hardware that is confused, this is not a very
graceful way to report that condition. It would be better to
make up a name to shelter kobject from the problem and to use an
error message that more precisely describes what happened.
Anyway, any changes in this direction will probably need to happen
upstream first, so the first step is to reproduce the problem with a
kernel that is closer to what they are working on. Please test
v2.6.39 or newer if possible (for example by using a wheezy d-i
image); if you have a working installation already, the only packages
from outside squeeze you should need in order to try it are the kernel
image itself, linux-base, and initramfs-tools.
Thanks for a nice report, and sorry for the very slow response.