On 03/01/2010 09:15 AM, Or Gerlitz wrote:
Or Gerlitz wrote:
Mike Christie wrote:

And we will have to watch out for a rmmod while there are ib_conns left

yes, I never was a big favor of rmmod flows, but, I admit they exist...

I do hit this -EEXIST race from time to time when running things like 
stop/start sequence.

Now I get it quite often but I am playing with the code. I am quite sure that
I saw this also on non modified occasions with latest kernels (e.g 2.6.30 and 
above)
did anyone else reported it as well?

Or.

Loading iSCSI transport class v2.0-870.
------------[ cut here ]------------
WARNING: at fs/sysfs/dir.c:487 sysfs_add_one+0xcc/0xe4()
Hardware name: X7DW3
sysfs: cannot create duplicate filename '/class/iscsi_endpoint'
Modules linked in: scsi_transport_iscsi(+) iw_cxgb3 cxgb3 mdio autofs4 nfs 
nfs_acl auth_rpcgss lockd sunrpc rds ib_ipoib rdma_ucm rdma_cm ib_ucm ib_uverbs 
ib_umad ib_cm iw_cm ib_addr ipv6 ib_sa dm_mirror dm_multipath video output 
battery ac joydev sr_mod sg igb ib_mthca ib_mad ib_core button floppy ioatdma 
rng_core pcspkr dca dm_region_hash dm_log dm_mod usb_storage ata_piix libata 
shpchp megaraid_sas sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd [last 
unloaded: scsi_transport_iscsi]
Pid: 5341, comm: modprobe Tainted: G        W  2.6.33 #1
Call Trace:
  [<ffffffff8110a4fc>] ? sysfs_add_one+0xcc/0xe4
  [<ffffffff810349a2>] ? warn_slowpath_common+0x77/0x8e
  [<ffffffff81034a15>] ? warn_slowpath_fmt+0x51/0x59
  [<ffffffff8110a428>] ? sysfs_pathname+0x35/0x3d
  [<ffffffff8110a428>] ? sysfs_pathname+0x35/0x3d
  [<ffffffff8110a4fc>] ? sysfs_add_one+0xcc/0xe4
  [<ffffffff8110a9f5>] ? create_dir+0x4f/0x85
  [<ffffffff8110aa60>] ? sysfs_create_dir+0x35/0x4a
  [<ffffffff8114a364>] ? kobject_add_internal+0xd2/0x18d
  [<ffffffff8114a443>] ? kset_register+0x24/0x3a
  [<ffffffffa0357000>] ? iscsi_transport_init+0x0/0x145 [scsi_transport_iscsi]
  [<ffffffff811e2f1a>] ? __class_register+0x128/0x1c0
  [<ffffffffa0357000>] ? iscsi_transport_init+0x0/0x145 [scsi_transport_iscsi]
  [<ffffffffa0357050>] ? iscsi_transport_init+0x50/0x145 [scsi_transport_iscsi]
  [<ffffffff810001e1>] ? do_one_initcall+0x50/0x13d
  [<ffffffff81060142>] ? sys_init_module+0xc8/0x222
  [<ffffffff81001eeb>] ? system_call_fastpath+0x16/0x1b
---[ end trace c8375848060e5033 ]---
kobject_add_internal failed for iscsi_endpoint with -EEXIST, don't try to 
register things with the same name in the same directory.
Pid: 5341, comm: modprobe Tainted: G        W  2.6.33 #1
Call Trace:
  [<ffffffff8114a3e0>] ? kobject_add_internal+0x14e/0x18d
  [<ffffffff8114a443>] ? kset_register+0x24/0x3a
  [<ffffffffa0357000>] ? iscsi_transport_init+0x0/0x145 [scsi_transport_iscsi]
  [<ffffffff811e2f1a>] ? __class_register+0x128/0x1c0
  [<ffffffffa0357000>] ? iscsi_transport_init+0x0/0x145 [scsi_transport_iscsi]
  [<ffffffffa0357050>] ? iscsi_transport_init+0x50/0x145 [scsi_transport_iscsi]
  [<ffffffff810001e1>] ? do_one_initcall+0x50/0x13d
  [<ffffffff81060142>] ? sys_init_module+0xc8/0x222
  [<ffffffff81001eeb>] ? system_call_fastpath+0x16/0x1b


I have not seen it. Something probably has iscsi_transport sysfs file open and so that object is not completely freed by the time you start up again. We see this error a lot with dm-multipath testing when paths (/dev/sdxs) are removed and added quickly.

--
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-is...@googlegroups.com.
To unsubscribe from this group, send email to 
open-iscsi+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/open-iscsi?hl=en.

Reply via email to