Devices not torn down properly
Devices not torn down properly
- Subject: Devices not torn down properly
- From: Nick Blievers <email@hidden>
- Date: Thu, 06 Dec 2007 14:03:39 +0800
Hi,
Not entirely sure this is the right mailing list, but here goes:
I have a system with a HBA connected to a bunch of luns, eg:
cc-mac1:~ root# fibreconfig -l
Controllers
PortWWN 10:00:00:06:2B:10:55:29
Port Status: Link Established
Speed: Automatic (2 Gigabit)
Topology: Automatic (N_Port)
Slot: Slot-2
Port: 1
PortWWN 10:00:00:06:2B:10:55:28
Port Status: No Link Established
Speed: Automatic
Topology: Automatic
Slot: Slot-2
Port: 0
Targets
NodeWWN 20:04:00:A0:B8:11:92:04
Status: Connected
LUNs: 0, 1, 2, 3, 4, 5
NodeWWN 20:05:00:A0:B8:26:2E:1E
Status: Connected
LUNs: 0, 1, 2, 3, 4, 5
NodeWWN 20:05:00:A0:B8:11:92:04
Status: Connected
LUNs: 0, 1, 2, 3, 4, 5
NodeWWN 20:04:00:A0:B8:26:2E:1E
Status: Connected
LUNs: 0, 1, 2, 3, 4, 5
cc-mac1:~ root# ls /dev/disk*
/dev/disk0 /dev/disk11 /dev/disk13s1 /dev/disk17
/dev/disk21 /dev/disk23s1 /dev/disk3 /dev/disk8
/dev/disk0s1 /dev/disk11s1 /dev/disk13s2 /dev/disk18
/dev/disk21s1 /dev/disk23s2 /dev/disk4 /dev/disk9
/dev/disk0s2 /dev/disk11s2 /dev/disk14 /dev/disk19
/dev/disk21s2 /dev/disk24 /dev/disk4s1
/dev/disk1 /dev/disk12 /dev/disk14s1 /dev/disk2
/dev/disk22 /dev/disk24s1 /dev/disk4s2
/dev/disk10 /dev/disk12s1 /dev/disk14s2 /dev/disk20
/dev/disk22s1 /dev/disk24s2 /dev/disk5
/dev/disk10s1 /dev/disk12s2 /dev/disk15 /dev/disk20s1
/dev/disk22s2 /dev/disk2s1 /dev/disk6
/dev/disk10s2 /dev/disk13 /dev/disk16 /dev/disk20s2
/dev/disk23 /dev/disk2s2 /dev/disk7
cc-mac1:~ root#
When the LUNs disappear (cable unplugged, or port disabled on the
switch), the /dev/disk* entries are removed after a period of time.
However, if the LUNs reappear (cable plugged back in, port enabled), the
/dev/disk* entries do not reappear (even after a long period of time):
cc-mac1:~ root# !fib
fibreconfig -l
Controllers
PortWWN 10:00:00:06:2B:10:55:29
Port Status: Link Established
Speed: Automatic (2 Gigabit)
Topology: Automatic (N_Port)
Slot: Slot-2
Port: 1
PortWWN 10:00:00:06:2B:10:55:28
Port Status: No Link Established
Speed: Automatic
Topology: Automatic
Slot: Slot-2
Port: 0
Targets
cc-mac1:~ root# ls /dev/disk*
/dev/disk0 /dev/disk0s1 /dev/disk0s2
cc-mac1:~ root#
Looking in the IORegistry, there are entries like the following:
| | | | | +-o IOSCSITargetDevice <class
IOSCSITargetDevice, !registered, !matched, inactive, busy 0, retain count 6>
| | | | | +-o IOSCSITargetDevice <class
IOSCSITargetDevice, !registered, !matched, inactive, busy 0, retain count 5>
| | | | | +-o IOSCSITargetDevice <class
IOSCSITargetDevice, !registered, !matched, inactive, busy 0, retain count 5>
| | | | +-o IOSCSITargetDevice <class
IOSCSITargetDevice, !registered, !matched, inactive, busy 0, retain count 5>
Which make we wonder if something is not getting torn down properly, and
hence when devices reappear they fail to get created properly.
This behaviour is not 100% consistent -- is there anything I can do
about it?
Thanks, and sorry for the long post
Nick
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden