Re: fc transport creates second set of targets for devices in an "md"

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

 




Michael Reed wrote:
> 
> James Smart wrote:
>> The data that would be most interesting is a recursive listing of the
>> device via the /sys/devices tree.  This would show the host, rports,
>> targets, and sdevs.  Getting a copy of this both before, when missing,
>> and after they are reconnected. The additional contents to look at
>> is : contents of /sys/class/fc_remote_ports.
> 
> I'll capture data and post later today.
> 

Attached.  ls_no_md.tar.bz2 and ls_with_md.tar.bz2

I noticed that more than just the devices associated with the
md were reassigned in the ls_with_md.tar output.

Mike

Attachment: ls_no_md.tar.bz2
Description: BZip2 compressed data

Attachment: ls_with_md.tar.bz2
Description: BZip2 compressed data


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux