Hey guys,
I've recently started playing around with LIO iSCSI and block devices on
LVM.
Now, after installing & configuring everything, all worked well & the
initiators were able to access the LUN as normal, however after a reboot of
the storage server, LIO seems to have trouble bringing it back up. I'm
getting no errors in the logs, and can't for the life of me work out what's
causing it.
Everything was working previously, the config was saved & everything still
seems to be configured correctly - so what's the issue? What could've
changed with a reboot?
The LVs are activated & available, & the LUN is configured under targetcli.
See below...
Targetcli:
o- / ............................................................ [...]
o- backstores ................................................. [...]
| o- fileio ...................................... [0 Storage Object]
| o- iblock ...................................... [1 Storage Object]
| | o- stor00 ......................... [/dev/vg0/stor00 deactivated]
| o- pscsi ....................................... [0 Storage Object]
| o- rd_dr ....................................... [0 Storage Object]
| o- rd_mcp ...................................... [0 Storage Object]
o- ib_srpt .............................................. [0 Targets]
o- iscsi ................................................. [1 Target]
| o- iqn.1995-01.com.example:dc0.stor00 ......................... [1 TPG]
| o- tpgt1 .............................................. [enabled]
| o- acls ............................................... [1 ACL]
| | o- iqn.1995-01.com.example:dc0 ................... [1 Mapped LUN]
| | o- mapped_lun0 .......................... [BROKEN LUN LINK]
| o- luns ............................................... [1 LUN]
| | o- lun0 ............................... [BROKEN STORAGE LINK]
| o- portals ......................................... [1 Portal]
| o- 10.20.200.28:3260 .................... [OK, iser disabled]
o- loopback ............................................. [0 Targets]
o- qla2xxx .............................................. [0 Targets]
o- tcm_fc ............................................... [0 Targets]
LVM:
root@stor0:/var/log# lvs
LV VG
Attr LSize Pool Origin Data% Move Log
Copy% Convert
LV-0d9b082b-71c8-4999-8b5c-e479f7d61867
VG_XenStorage-a53629f8-dd21-5dcf-6fa0-8ebec213f2f8 -wi-a---- 256,00m
LV-470c4026-a950-4860-9232-d6cf225198a2
VG_XenStorage-a53629f8-dd21-5dcf-6fa0-8ebec213f2f8 -wi-a---- 4,00m
MGT
VG_XenStorage-a53629f8-dd21-5dcf-6fa0-8ebec213f2f8 -wi-a---- 4,00m
VHD-1f276101-f6fb-4fb9-9b86-4537d2187421
VG_XenStorage-a53629f8-dd21-5dcf-6fa0-8ebec213f2f8 -wi-a---- 20,05g
VHD-e0028b47-0100-4f76-999c-133021eaf97f
VG_XenStorage-a53629f8-dd21-5dcf-6fa0-8ebec213f2f8 -wi-a---- 30,07g
VHD-ee4f8685-2e75-452d-a1e8-2145a8730d25
VG_XenStorage-a53629f8-dd21-5dcf-6fa0-8ebec213f2f8 -wi-a---- 15,04g
root vg0
-wi-ao--- 9,31g
stor00 vg0
-wi-ao--- 1,32t
swap vg0
-wi-ao--- 3,72g
tmp vg0
-wi-ao--- 9,31g
var vg0
-wi-ao--- 5,00g
root@stor0:/var/log#
Anyone got any ideas? Why's the LUN designated as "broken"?
Many thanks in advance!
--
Doug
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
