On Wed, Jun 13, 2018 at 8:33 AM, Wladimir Mutel <m...@mwg.dp.ua> wrote:
> On Tue, Jun 12, 2018 at 10:39:59AM -0400, Jason Dillaman wrote:
>
>> > So, my usual question is - where to look and what logs to enable
>> > to find out what is going wrong ?
>
>> If not overridden, tcmu-runner will default to 'client.admin' [1] so
>> you shouldn't need to add any additional caps. In the short-term to
>> debug your issue, you can perhaps increase the log level for
>> tcmu-runner to see if it's showing an error [2].
>
> So, I put 'log_level = 5' into /etc/tcmu/tcmu.conf , restart
> tcmu0runner and see only this in its logs :
>
> чер 13 08:38:14 p10s systemd[1]: Starting LIO Userspace-passthrough daemon...
> чер 13 08:38:14 p10s tcmu-runner[54121]: Inotify is watching
> "/etc/tcmu/tcmu.conf", wd: 1, mask: IN_ALL_EVENTS
> чер 13 08:38:14 p10s tcmu-runner[54121]: 2018-06-13 08:38:14.634 54121
> [DEBUG] load_our_module:531: Module 'target_core_user' is already loaded
> чер 13 08:38:14 p10s tcmu-runner[54121]: 2018-06-13 08:38:14.634 54121
> [DEBUG] main:1087: handler path: /usr/lib/x86_64-linux-gnu/tcmu-runner
> чер 13 08:38:14 p10s tcmu-runner[54121]: 2018-06-13 08:38:14.657 54121
> [DEBUG] main:1093: 2 runner handlers found
> чер 13 08:38:14 p10s tcmu-runner[54121]: 2018-06-13 08:38:14.658 54121
> [DEBUG] tcmu_block_device:404 rbd/libvirt.tower-prime-e-3tb: blocking kernel
> device
> чер 13 08:38:14 p10s tcmu-runner[54121]: 2018-06-13 08:38:14.658 54121
> [DEBUG] tcmu_block_device:410 rbd/libvirt.tower-prime-e-3tb: block done
> чер 13 08:38:14 p10s tcmu-runner[54121]: 2018-06-13 08:38:14.658 54121
> [DEBUG] dev_added:769 rbd/libvirt.tower-prime-e-3tb: Got block_size 512, size
> in bytes 3000596692992
> чер 13 08:38:14 p10s tcmu-runner[54121]: 2018-06-13 08:38:14.658 54121
> [DEBUG] tcmu_rbd_open:829 rbd/libvirt.tower-prime-e-3tb: tcmu_rbd_open config
> rbd/libvirt/tower-prime-e-3tb;osd_op_timeout=30 block size 512 num lbas
> 5860540416.
> чер 13 08:38:14 p10s tcmu-runner[54121]: 2018-06-13 08:38:14.665 54121
> [DEBUG] timer_check_and_set_def:383 rbd/libvirt.tower-prime-e-3tb: The
> cluster's default osd op timeout(0.000000), osd heartbeat grace(20)
> interval(6)
> чер 13 08:38:14 p10s tcmu-runner[54121]: 2018-06-13 08:38:14.672 54121
> [DEBUG] tcmu_rbd_detect_device_class:300 rbd/libvirt.tower-prime-e-3tb: Pool
> libvirt using crush rule "replicated_rule"
> чер 13 08:38:14 p10s tcmu-runner[54121]: 2018-06-13 08:38:14.672 54121
> [DEBUG] tcmu_rbd_detect_device_class:316 rbd/libvirt.tower-prime-e-3tb: SSD
> not a registered device class.
> чер 13 08:38:14 p10s tcmu-runner[54121]: 2018-06-13 08:38:14.715 7f30e08c9880
> 1 mgrc service_daemon_register tcmu-runner.p10s:libvirt/tower-prime-e-3tb
> metadata {arch=x86_64,ceph_release=mimic,ceph_version=ceph version 13.2.0
> (79a10589f1f80dfe21e8f9794365ed98143071c4) mimic
> (stable),ceph_version_short=13.2.0,cpu=Intel(R) Xeon(R) CPU E3-1235L v5 @
> 2.00GHz,distro=ubuntu,distro_description=Ubuntu 18.04
> LTS,distro_version=18.04,hostname=p10s,image_id=25c21238e1f29,image_name=tower-prime-e-3tb,kernel_description=#201806032231
> SMP Sun Jun 3 22:33:34 UTC
> 2018,kernel_version=4.17.0-041700-generic,mem_swap_kb=15622140,mem_total_kb=65827836,os=Linux,pool_name=libvirt}
> чер 13 08:38:14 p10s tcmu-runner[54121]: 2018-06-13 08:38:14.721 54121
> [DEBUG] tcmu_unblock_device:422 rbd/libvirt.tower-prime-e-3tb: unblocking
> kernel device
> чер 13 08:38:14 p10s tcmu-runner[54121]: 2018-06-13 08:38:14.721 54121
> [DEBUG] tcmu_unblock_device:428 rbd/libvirt.tower-prime-e-3tb: unblock done
> чер 13 08:38:14 p10s tcmu-runner[54121]: 2018-06-13 08:38:14.724 54121
> [DEBUG] dbus_bus_acquired:445: bus org.kernel.TCMUService1 acquired
> чер 13 08:38:14 p10s systemd[1]: Started LIO Userspace-passthrough daemon.
> чер 13 08:38:14 p10s tcmu-runner[54121]: 2018-06-13 08:38:14.726 54121
> [DEBUG] dbus_name_acquired:461: name org.kernel.TCMUService1 acquired
> чер 13 08:38:30 p10s tcmu-runner[54121]: 2018-06-13 08:38:30.521 54121
> [DEBUG_SCSI_CMD] tcmu_print_cdb_info:1205 rbd/libvirt.tower-prime-e-3tb: 1a 0
> 3f 0 c0 0
> чер 13 08:38:30 p10s tcmu-runner[54121]: 2018-06-13 08:38:30.523 54121
> [DEBUG_SCSI_CMD] tcmu_print_cdb_info:1205 rbd/libvirt.tower-prime-e-3tb: 1a 0
> 3f 0 c0 0
> чер 13 08:38:30 p10s tcmu-runner[54121]: 2018-06-13 08:38:30.543 54121
> [DEBUG_SCSI_CMD] tcmu_print_cdb_info:1205 rbd/libvirt.tower-prime-e-3tb: 9e
> 10 0 0 0 0 0 0 0 0 0 0 0 c 0 0
> чер 13 08:38:30 p10s tcmu-runner[54121]: 2018-06-13 08:38:30.550 54121
> [DEBUG_SCSI_CMD] tcmu_print_cdb_info:1205 rbd/libvirt.tower-prime-e-3tb: 9e
> 10 0 0 0 0 0 0 0 0 0 0 0 c 0 0
> чер 13 08:38:47 p10s tcmu-runner[54121]: 2018-06-13 08:38:47.944 54121
> [DEBUG_SCSI_CMD] tcmu_print_cdb_info:1205 rbd/libvirt.tower-prime-e-3tb: 9e
> 10 0 0 0 0 0 0 0 0 0 0 0 c 0 0
>
> Wikipedia says that 1A is 'mode sense' and 9e is 'service action in'.
> These records are logged when I try to put the disk online or
> initialize it with GPT/MBR partition table in Windows Disk Management (and
> Windows report errors after that)
> What to check next ? Any importance of missing 'SSD' device class ?
Did you configure MPIO within Windows [1]? Any errors recorded in the
Windows Event Viewer?
The "SSD" device class isn't important -- it's just a way to describe
the LUN as being backed by non-rotational media (e.g. VMware will show
a different icon).
> _______________________________________________
> ceph-users mailing list
> ceph-users@lists.ceph.com
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
[1] http://docs.ceph.com/docs/master/rbd/iscsi-initiator-win/
--
Jason
_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
