On Mon, 2009-08-24 at 17:29 +0530, Lokanadham P-TLS,Chennai wrote: > Hi All, > I am using the Open fcoe Initiator (2.6.29.1), Open Solaris Target (build > 119) and cisco nexus FCF. Both the initiator and target connected to FCF > through Ethernet switch. > > I have installed the open fcoe initiator user space tools and dcdb also. And > I enabled the pause mechanism in the initiator machine. > I'm curious about this statement. How did you enable pause on the initiator? Using dcbtool, ethtool or are you talking about configuring it in your .config file? You'll either be using link-pause or per-priority-pause (i.e. DCB). Which do you intend to use? I'll continue under the assumption that you're using PPP since you've got a proper FCF.
> I am creating the LUNS on the solaris target. And I am also able > to see those LUNS on the initiator when I do lsscsi, > > I made the ext2 file system on the discovered LUN, when I tried > to mount the discover LUN it's giving below error: > > mount: wrong fs type, bad option, bad superblock on /dev/sdb, > missing codepage or helper program, or other error > In some cases useful info is found in syslog - try > dmesg | tail or so > > How do I do the actual data transfer to the target and how to > verify that? > It sounds like something got goofed up when you made your filesystem. Lets make sure that the filesystem actually got written to the disk correctly. I'm curious what dmesg looks like after you've formatted the disk. I'm not sure if the mkfs is included in the log below, but assuming that it is then you can see there are SCSI errors when you're interacting with the LUN. The READ_CAPACITY fails and that's really bad. This seems like it's a configuration problem. Can you run the <fcoe-utils.git>/debug/dcbcheck.sh script and make sure that it says DCB is configured correctly? DCB is the first thing to check from the initiator side, but unfortunately I haven't seen bad DCB configurations cause so many errors. Usually there will only be intermittent errors. You should probably double check your target setup. Also, does the target provide any logs that might give us a clue? > > Output of lsscsi from initiator Machine: > [0:0:0:0] disk ATA ST340015A 3.01 > /dev/sda > [3:0:0:1] disk SUN COMSTAR 1.0 /dev/sdb > > Dmesg Out put from the Open-fcoe Initiator: > > scsi2 : FCoE Driver > libfc: Link up on port ( 0) > libfcoe: host2: FIP selected Fibre-Channel Forwarder MAC 00:02:a5:4e:96:65 > libfc: Assigned FID ( 10201) in FLOGI response > scsi3 : FCoE Driver > libfc: Link up on port ( 0) > libfcoe: host3: FIP selected Fibre-Channel Forwarder MAC 00:02:a5:4e:96:65 > libfc: Assigned FID ( 10201) in FLOGI response > scsi 3:0:0:1: Direct-Access SUN COMSTAR 1.0 PQ: 0 ANSI: 5 > sd 3:0:0:1: Attached scsi generic sg1 type 0 > sd 3:0:0:1: [sdb] READ CAPACITY(16) failed > sd 3:0:0:1: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK > sd 3:0:0:1: [sdb] Sense not available. > sd 3:0:0:1: [sdb] 7139200 512-byte logical blocks: (3.65 GB/3.40 GiB) > sd 3:0:0:1: [sdb] Write Protect is off > sd 3:0:0:1: [sdb] Mode Sense: 53 00 00 00 > sd 3:0:0:1: [sdb] Write cache: enabled, read cache: enabled, doesn't support > DPO or FUA > sd 3:0:0:1: [sdb] READ CAPACITY(16) failed > sd 3:0:0:1: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK > sd 3:0:0:1: [sdb] Sense not available. > sdb: > sd 3:0:0:1: [sdb] Unhandled error code > sd 3:0:0:1: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > end_request: I/O error, dev sdb, sector 0 > Buffer I/O error on device sdb, logical block 0 > sd 3:0:0:1: [sdb] Unhandled error code > sd 3:0:0:1: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > end_request: I/O error, dev sdb, sector 0 > Buffer I/O error on device sdb, logical block 0 > sd 3:0:0:1: [sdb] Unhandled error code > sd 3:0:0:1: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > end_request: I/O error, dev sdb, sector 0 > Buffer I/O error on device sdb, logical block 0 > sd 3:0:0:1: [sdb] Unhandled error code > sd 3:0:0:1: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > end_request: I/O error, dev sdb, sector 0 > Buffer I/O error on device sdb, logical block 0 > sd 3:0:0:1: [sdb] Unhandled error code > sd 3:0:0:1: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > end_request: I/O error, dev sdb, sector 0 > Buffer I/O error on device sdb, logical block 0 > sd 3:0:0:1: [sdb] Unhandled error code > sd 3:0:0:1: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > end_request: I/O error, dev sdb, sector 0 > Buffer I/O error on device sdb, logical block 0 > sd 3:0:0:1: [sdb] Unhandled error code > sd 3:0:0:1: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > end_request: I/O error, dev sdb, sector 0 > Buffer I/O error on device sdb, logical block 0 > Dev sdb: unable to read RDB block 0 > sd 3:0:0:1: [sdb] Unhandled error code > sd 3:0:0:1: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > end_request: I/O error, dev sdb, sector 0 > Buffer I/O error on device sdb, logical block 0 > sd 3:0:0:1: [sdb] Unhandled error code > sd 3:0:0:1: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > end_request: I/O error, dev sdb, sector 0 > Buffer I/O error on device sdb, logical block 0 > unable to read partition table > sd 3:0:0:1: [sdb] READ CAPACITY(16) failed > sd 3:0:0:1: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK > sd 3:0:0:1: [sdb] Sense not available. > sd 3:0:0:1: [sdb] Attached SCSI disk > sd 3:0:0:1: [sdb] Unhandled error code > sd 3:0:0:1: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > end_request: I/O error, dev sdb, sector 7139072 > Buffer I/O error on device sdb, logical block 892384 > sd 3:0:0:1: [sdb] Unhandled error code > sd 3:0:0:1: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > end_request: I/O error, dev sdb, sector 0 > Buffer I/O error on device sdb, logical block 0 > Buffer I/O error on device sdb, logical block 1 > Buffer I/O error on device sdb, logical block 2 > Buffer I/O error on device sdb, logical block 3 > sd 3:0:0:1: [sdb] Unhandled error code > sd 3:0:0:1: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > end_request: I/O error, dev sdb, sector 0 > Buffer I/O error on device sdb, logical block 0 > sd 3:0:0:1: [sdb] Unhandled error code > sd 3:0:0:1: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > end_request: I/O error, dev sdb, sector 7139192 > Buffer I/O error on device sdb, logical block 892399 > sd 3:0:0:1: [sdb] Unhandled error code > sd 3:0:0:1: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > end_request: I/O error, dev sdb, sector 0 > sd 3:0:0:1: [sdb] Unhandled error code > sd 3:0:0:1: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > end_request: I/O error, dev sdb, sector 7139192 > Buffer I/O error on device sdb, logical block 892399 > sd 3:0:0:1: [sdb] Unhandled error code > sd 3:0:0:1: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK > end_request: I/O error, dev sdb, sector 384 > sd 3:0:0:1: [sdb] Unhandled error code > sd 3:0:0:1: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > end_request: I/O error, dev sdb, sector 88 > sd 3:0:0:1: [sdb] Unhandled error code > sd 3:0:0:1: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK > end_request: I/O error, dev sdb, sector 384 > sd 3:0:0:1: [sdb] Unhandled error code > sd 3:0:0:1: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > end_request: I/O error, dev sdb, sector 0 > Buffer I/O error on device sdb, logical block 0 > Buffer I/O error on device sdb, logical block 1 > Buffer I/O error on device sdb, logical block 2 > Buffer I/O error on device sdb, logical block 3 > Buffer I/O error on device sdb, logical block 4 > Buffer I/O error on device sdb, logical block 5 > Buffer I/O error on device sdb, logical block 6 > Buffer I/O error on device sdb, logical block 7 > Buffer I/O error on device sdb, logical block 8 > sd 3:0:0:1: [sdb] Unhandled error code > sd 3:0:0:1: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > > > Thanks > Lokanadham > > DISCLAIMER: > ----------------------------------------------------------------------------------------------------------------------- > > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. > It shall not attach any liability on the originator or HCL or its affiliates. > Any views or opinions presented in > this email are solely those of the author and may not necessarily reflect the > opinions of HCL or its affiliates. > Any form of reproduction, dissemination, copying, disclosure, modification, > distribution and / or publication of > this message without the prior written consent of the author of this e-mail > is strictly prohibited. If you have > received this email in error please delete it and notify the sender > immediately. Before opening any mail and > attachments please check them for viruses and defect. > > ----------------------------------------------------------------------------------------------------------------------- > _______________________________________________ > devel mailing list > [email protected] > http://www.open-fcoe.org/mailman/listinfo/devel _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
