[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[dm-devel] path coalescing once more



We continue to run into problems with the device-mapper presumably putting LUNs which do not belong with the dm under its control. Here is the latest (I am picking out just dm-2 but there are others in this same state):

3624a9370c90d0d631ef8783e00010004 dm-2 PURE,FlashArray
size=500G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
  |- 7:0:0:3 sdj  8:144  active ready running
  |- 3:0:0:3 sdba 67:64  active ready running
  |- 0:0:0:3 sdaz 67:48  active ready running
  |- 5:0:0:3 sdbb 67:80  active ready running
  |- 6:0:0:3 sdcc 69:0   active ready running
  |- 1:0:0:1 sdaj 66:48  active ready running
  `- 2:0:0:1 sdbv 68:144 active ready running

I see the following kernel messages in the syslog when the device sdaj arrives to when it is put in the wrong place:
May 13 11:28:27 rb9init4 kernel: scsi 1:0:0:1: Direct-Access     PURE     FlashArray       400B PQ: 0 ANSI: 6
May 13 11:28:27 rb9init4 kernel: sd 1:0:0:1: [sdaj] 1048576000 512-byte logical blocks: (536 GB/500 GiB)
May 13 11:28:27 rb9init4 kernel: sd 1:0:0:1: Attached scsi generic sg1 type 0
May 13 11:28:27 rb9init4 kernel: sd 1:0:0:1: [sdaj] Write Protect is off
May 13 11:28:27 rb9init4 kernel: sd 1:0:0:1: [sdaj] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
May 13 11:28:27 rb9init4 kernel: sdaj:
May 13 11:28:27 rb9init4 kernel: unknown partition table
May 13 11:28:27 rb9init4 kernel: sd 1:0:0:1: [sdaj] Attached SCSI disk
May 13 11:28:28 rb9init4 multipathd: sdaj: add path (uevent)
May 13 11:28:28 rb9init4 multipathd: sdaj path added to devmap 3624a9370c90d0d631ef8783e00010004

I don’t understand where it gets 3624a9370c90d0d631ef8783e00010004. When I run the ‘multipath -v6 -d’ so that it prints out what it wants to do but doesn’t do it, I see:
May 13 16:45:15 | Discover device /sys/block/sdaj
May 13 16:45:15 | sdaj: not found in pathvec
May 13 16:45:15 | sdaj: mask = 0x3f
May 13 16:45:15 | sdaj: dev_t = 66:48
May 13 16:45:15 | sdaj: size = 1048576000
May 13 16:45:15 | sdaj: subsystem = scsi
May 13 16:45:15 | sdaj: vendor = PURE
May 13 16:45:15 | sdaj: product = FlashArray
May 13 16:45:15 | sdaj: rev = 400B
May 13 16:45:15 | sdaj: h:b:t:l = 1:0:0:1
May 13 16:45:15 | sdaj: tgt_node_name = 0x524a937000016901
May 13 16:45:15 | sdaj: serial = C90D0D631EF8783E00010002
May 13 16:45:15 | sdaj: get_state
May 13 16:45:15 | loading /lib64/multipath/libchecktur.so checker
May 13 16:45:15 | sdaj: path checker = tur (controller setting)
May 13 16:45:15 | sdaj: checker timeout = 30000 ms (sysfs setting)
May 13 16:45:15 | sdaj: state = running
May 13 16:45:15 | sdaj: state = 3
May 13 16:45:15 | sdaj: getuid = /lib/udev/scsi_id --whitelisted --device=/dev/%n (config file default)
May 13 16:45:15 | sdaj: uid = 3624a9370c90d0d631ef8783e00010002 (callout)
May 13 16:45:15 | sdaj: state = running
May 13 16:45:15 | sdaj: detect_prio = 1 (config file default)
May 13 16:45:15 | sdaj: prio = const (config file default)
May 13 16:45:15 | sdaj: const prio = 1

So it seems to know thats its serial ends in “02” and not “04” like where it put the device. I don’t understand how to debug this further, so any help would be appreciated.

Thanks,
Brian


Brian Bunker




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]