5:41 p.m.
This is a multi-part message in MIME format.
--------------050203060205030209020801
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Hi, next explanation
VDSM log give me following message
Is this live checking for storage availability ? If "SUCCESS" then why
"<err> " ???
regs.
Pavel
Thread-233::DEBUG::2016-03-02
17:31:55,275::fileSD::262::Storage.Misc.excCmd::(getReadDelay) SUCCESS:
<err> = '0+1 records in\n0+1 records out\n346 bytes (346 B) copied,
0.00022692 s, 1.5 MB/s\n'; <rc> = 0
Thread-299::DEBUG::2016-03-02
17:31:57,870::fileSD::262::Storage.Misc.excCmd::(getReadDelay)
/usr/bin/dd
if=/rhev/data-center/mnt/glusterSD/localhost:_2KVM12__P4/300e9ac8-3c2f-4703-9bb1-1df2130c7c97/dom_md/metadata
iflag=direct of=/dev/null bs=4096 count=1 (cwd None)
Thread-299::DEBUG::2016-03-02
17:31:57,886::fileSD::262::Storage.Misc.excCmd::(getReadDelay) SUCCESS:
<err> = '0+1 records in\n0+1 records out\n734 bytes (734 B) copied,
0.000391403 s, 1.9 MB/s\n'; <rc> = 0
Thread-209::DEBUG::2016-03-02
17:31:58,301::fileSD::262::Storage.Misc.excCmd::(getReadDelay)
/usr/bin/dd
if=/rhev/data-center/mnt/glusterSD/localhost:_1KVM12-BCK/0fcad888-d573-47be-bef3-0bc0b7a99fb7/dom_md/metadata
iflag=direct of=/dev/null bs=4096 count=1 (cwd None)
Thread-209::DEBUG::2016-03-02
17:31:58,318::fileSD::262::Storage.Misc.excCmd::(getReadDelay) SUCCESS:
<err> = '0+1 records in\n0+1 records out\n335 bytes (335 B) copied,
0.00048095 s, 697 kB/s\n'; <rc> = 0
Thread-198::DEBUG::2016-03-02
17:31:58,885::fileSD::262::Storage.Misc.excCmd::(getReadDelay)
/usr/bin/dd
if=/rhev/data-center/mnt/installshare:_DATA3/7f334c9d-ac01-4b2a-9f29-af1d2f24c3e0/dom_md/metadata
iflag=direct of=/dev/null bs=4096 count=1 (cwd None)
dist = RHEL - 7 - 2.1511
kernel = 3.10.0 - 327.10.1.el7.x86_64
KVM = 2.3.0 - 29.1.el7
libvirt = libvirt-1.2.17-13.el7_2.3
vdsm = vdsm-4.16.30-0.el7
GlusterFS = glusterfs-3.7.8-1.el7
--------------050203060205030209020801
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=utf-8">
</head>
<body text="#000066" bgcolor="#FFFFFF">
Hi, next explanation<br>
VDSM log give me following message<br>
Is this live checking for storage availability ? If "SUCCESS" then
why "<err> " ???<br>
<br>
regs.<br>
Pavel<br>
<br>
Thread-233::DEBUG::2016-03-02
17:31:55,275::fileSD::262::Storage.Misc.excCmd::(getReadDelay)
SUCCESS: <err> = '0+1 records in\n0+1 records out\n346 bytes
(346 B) copied, 0.00022692 s, 1.5 MB/s\n'; <rc> = 0<br>
Thread-299::DEBUG::2016-03-02
17:31:57,870::fileSD::262::Storage.Misc.excCmd::(getReadDelay)
/usr/bin/dd
if=/rhev/data-center/mnt/glusterSD/localhost:_2KVM12__P4/300e9ac8-3c2f-4703-9bb1-1df2130c7c97/dom_md/metadata
iflag=direct of=/dev/null bs=4096 count=1 (cwd None)<br>
Thread-299::DEBUG::2016-03-02
17:31:57,886::fileSD::262::Storage.Misc.excCmd::(getReadDelay)
SUCCESS: <err> = '0+1 records in\n0+1 records out\n734 bytes
(734 B) copied, 0.000391403 s, 1.9 MB/s\n'; <rc> = 0<br>
Thread-209::DEBUG::2016-03-02
17:31:58,301::fileSD::262::Storage.Misc.excCmd::(getReadDelay)
/usr/bin/dd
if=/rhev/data-center/mnt/glusterSD/localhost:_1KVM12-BCK/0fcad888-d573-47be-bef3-0bc0b7a99fb7/dom_md/metadata
iflag=direct of=/dev/null bs=4096 count=1 (cwd None)<br>
Thread-209::DEBUG::2016-03-02
17:31:58,318::fileSD::262::Storage.Misc.excCmd::(getReadDelay)
SUCCESS: <err> = '0+1 records in\n0+1 records out\n335 bytes
(335 B) copied, 0.00048095 s, 697 kB/s\n'; <rc> = 0<br>
Thread-198::DEBUG::2016-03-02
17:31:58,885::fileSD::262::Storage.Misc.excCmd::(getReadDelay)
/usr/bin/dd
if=/rhev/data-center/mnt/installshare:_DATA3/7f334c9d-ac01-4b2a-9f29-af1d2f24c3e0/dom_md/metadata
iflag=direct of=/dev/null bs=4096 count=1 (cwd None)<br>
<br>
dist = RHEL - 7 - 2.1511<br>
kernel = 3.10.0 - 327.10.1.el7.x86_64<br>
KVM = 2.3.0 - 29.1.el7<br>
libvirt = libvirt-1.2.17-13.el7_2.3<br>
vdsm = vdsm-4.16.30-0.el7<br>
GlusterFS = glusterfs-3.7.8-1.el7<br>
</body>
</html>
--------------050203060205030209020801--
5:56 p.m.
This is a multi-part message in MIME format.
--------------080009010404090302000105
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Hi,
in general, programs use stderr (which you see after <err>) to output
miscellaneous information. You can see here that "dd" is an example of
this behaviour. While it exited successfully, it also wrote
non-essential information to its secondary output. You do not see stdout
(the primary channel) in the log because "dd" doesn't use it in this case.
Cheers,
Ondra
On 2.3.2016 17:41, paf1(a)email.cz wrote:
Hi, next explanation
VDSM log give me following message
Is this live checking for storage availability ? If "SUCCESS" then why
"<err> " ???
regs.
Pavel
Thread-233::DEBUG::2016-03-02
17:31:55,275::fileSD::262::Storage.Misc.excCmd::(getReadDelay)
SUCCESS: <err> = '0+1 records in\n0+1 records out\n346 bytes (346 B)
copied, 0.00022692 s, 1.5 MB/s\n'; <rc> = 0
Thread-299::DEBUG::2016-03-02
17:31:57,870::fileSD::262::Storage.Misc.excCmd::(getReadDelay)
/usr/bin/dd
if=/rhev/data-center/mnt/glusterSD/localhost:_2KVM12__P4/300e9ac8-3c2f-4703-9bb1-1df2130c7c97/dom_md/metadata
iflag=direct of=/dev/null bs=4096 count=1 (cwd None)
Thread-299::DEBUG::2016-03-02
17:31:57,886::fileSD::262::Storage.Misc.excCmd::(getReadDelay)
SUCCESS: <err> = '0+1 records in\n0+1 records out\n734 bytes (734 B)
copied, 0.000391403 s, 1.9 MB/s\n'; <rc> = 0
Thread-209::DEBUG::2016-03-02
17:31:58,301::fileSD::262::Storage.Misc.excCmd::(getReadDelay)
/usr/bin/dd
if=/rhev/data-center/mnt/glusterSD/localhost:_1KVM12-BCK/0fcad888-d573-47be-bef3-0bc0b7a99fb7/dom_md/metadata
iflag=direct of=/dev/null bs=4096 count=1 (cwd None)
Thread-209::DEBUG::2016-03-02
17:31:58,318::fileSD::262::Storage.Misc.excCmd::(getReadDelay)
SUCCESS: <err> = '0+1 records in\n0+1 records out\n335 bytes (335 B)
copied, 0.00048095 s, 697 kB/s\n'; <rc> = 0
Thread-198::DEBUG::2016-03-02
17:31:58,885::fileSD::262::Storage.Misc.excCmd::(getReadDelay)
/usr/bin/dd
if=/rhev/data-center/mnt/installshare:_DATA3/7f334c9d-ac01-4b2a-9f29-af1d2f24c3e0/dom_md/metadata
iflag=direct of=/dev/null bs=4096 count=1 (cwd None)
dist = RHEL - 7 - 2.1511
kernel = 3.10.0 - 327.10.1.el7.x86_64
KVM = 2.3.0 - 29.1.el7
libvirt = libvirt-1.2.17-13.el7_2.3
vdsm = vdsm-4.16.30-0.el7
GlusterFS = glusterfs-3.7.8-1.el7
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--------------080009010404090302000105
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi,<br>
<br>
in general, programs use stderr (which you see after <err>) to
output miscellaneous information. You can see here that "dd" is an
example of this behaviour. While it exited successfully, it also
wrote non-essential information to its secondary output. You do not
see stdout (the primary channel) in the log because "dd" doesn't use
it in this case.<br>
<br>
Cheers,<br>
Ondra<br>
<br>
<div class="moz-cite-prefix">On 2.3.2016 17:41, <a
class="moz-txt-link-abbreviated"
href="mailto:paf1@email.cz">paf1@email.cz</a> wrote:<br>
</div>
<blockquote cite="mid:56D717BA.2080706@email.cz"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
Hi, next explanation<br>
VDSM log give me following message<br>
Is this live checking for storage availability ? If "SUCCESS"
then why "<err> " ???<br>
<br>
regs.<br>
Pavel<br>
<br>
Thread-233::DEBUG::2016-03-02
17:31:55,275::fileSD::262::Storage.Misc.excCmd::(getReadDelay)
SUCCESS: <err> = '0+1 records in\n0+1 records out\n346 bytes
(346 B) copied, 0.00022692 s, 1.5 MB/s\n'; <rc> = 0<br>
Thread-299::DEBUG::2016-03-02
17:31:57,870::fileSD::262::Storage.Misc.excCmd::(getReadDelay)
/usr/bin/dd
if=/rhev/data-center/mnt/glusterSD/localhost:_2KVM12__P4/300e9ac8-3c2f-4703-9bb1-1df2130c7c97/dom_md/metadata
iflag=direct of=/dev/null bs=4096 count=1 (cwd None)<br>
Thread-299::DEBUG::2016-03-02
17:31:57,886::fileSD::262::Storage.Misc.excCmd::(getReadDelay)
SUCCESS: <err> = '0+1 records in\n0+1 records out\n734 bytes
(734 B) copied, 0.000391403 s, 1.9 MB/s\n'; <rc> = 0<br>
Thread-209::DEBUG::2016-03-02
17:31:58,301::fileSD::262::Storage.Misc.excCmd::(getReadDelay)
/usr/bin/dd
if=/rhev/data-center/mnt/glusterSD/localhost:_1KVM12-BCK/0fcad888-d573-47be-bef3-0bc0b7a99fb7/dom_md/metadata
iflag=direct of=/dev/null bs=4096 count=1 (cwd None)<br>
Thread-209::DEBUG::2016-03-02
17:31:58,318::fileSD::262::Storage.Misc.excCmd::(getReadDelay)
SUCCESS: <err> = '0+1 records in\n0+1 records out\n335 bytes
(335 B) copied, 0.00048095 s, 697 kB/s\n'; <rc> = 0<br>
Thread-198::DEBUG::2016-03-02
17:31:58,885::fileSD::262::Storage.Misc.excCmd::(getReadDelay)
/usr/bin/dd
if=/rhev/data-center/mnt/installshare:_DATA3/7f334c9d-ac01-4b2a-9f29-af1d2f24c3e0/dom_md/metadata
iflag=direct of=/dev/null bs=4096 count=1 (cwd None)<br>
<br>
dist = RHEL - 7 - 2.1511<br>
kernel = 3.10.0 - 327.10.1.el7.x86_64<br>
KVM = 2.3.0 - 29.1.el7<br>
libvirt = libvirt-1.2.17-13.el7_2.3<br>
vdsm = vdsm-4.16.30-0.el7<br>
GlusterFS = glusterfs-3.7.8-1.el7<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated"
href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a class="moz-txt-link-freetext"
href="http://lists.ovirt.org/mailman/listinfo/users">http://...
</pre>
</blockquote>
<br>
</body>
</html>
--------------080009010404090302000105--
8:07 p.m.
On Wed, Mar 2, 2016 at 6:41 PM, paf1(a)email.cz <paf1(a)email.cz> wrote:
Hi, next explanation
VDSM log give me following message
Is this live checking for storage availability ? If "SUCCESS" then why
"<err> " ???
- SUCCESS means the command was successful
- <err> is what the command wrote to stderr, which is sometimes useful
This is indeed confusing and wrong - there is not need to log stderr of all
commands
by default. In the case of this dd command, the read latency is reported
later in repoStats
logs.
We will clean this in the future.
Nir
regs.
Pavel
Thread-233::DEBUG::2016-03-02
17:31:55,275::fileSD::262::Storage.Misc.excCmd::(getReadDelay) SUCCESS:
<err> = '0+1 records in\n0+1 records out\n346 bytes (346 B) copied,
0.00022692 s, 1.5 MB/s\n'; <rc> = 0
Thread-299::DEBUG::2016-03-02
17:31:57,870::fileSD::262::Storage.Misc.excCmd::(getReadDelay) /usr/bin/dd
if=/rhev/data-center/mnt/glusterSD/localhost:_2KVM12__P4/300e9ac8-3c2f-4703-9bb1-1df2130c7c97/dom_md/metadata
iflag=direct of=/dev/null bs=4096 count=1 (cwd None)
Thread-299::DEBUG::2016-03-02
17:31:57,886::fileSD::262::Storage.Misc.excCmd::(getReadDelay) SUCCESS:
<err> = '0+1 records in\n0+1 records out\n734 bytes (734 B) copied,
0.000391403 s, 1.9 MB/s\n'; <rc> = 0
Thread-209::DEBUG::2016-03-02
17:31:58,301::fileSD::262::Storage.Misc.excCmd::(getReadDelay) /usr/bin/dd
if=/rhev/data-center/mnt/glusterSD/localhost:_1KVM12-BCK/0fcad888-d573-47be-bef3-0bc0b7a99fb7/dom_md/metadata
iflag=direct of=/dev/null bs=4096 count=1 (cwd None)
Thread-209::DEBUG::2016-03-02
17:31:58,318::fileSD::262::Storage.Misc.excCmd::(getReadDelay) SUCCESS:
<err> = '0+1 records in\n0+1 records out\n335 bytes (335 B) copied,
0.00048095 s, 697 kB/s\n'; <rc> = 0
Thread-198::DEBUG::2016-03-02
17:31:58,885::fileSD::262::Storage.Misc.excCmd::(getReadDelay) /usr/bin/dd
if=/rhev/data-center/mnt/installshare:_DATA3/7f334c9d-ac01-4b2a-9f29-af1d2f24c3e0/dom_md/metadata
iflag=direct of=/dev/null bs=4096 count=1 (cwd None)
dist = RHEL - 7 - 2.1511
kernel = 3.10.0 - 327.10.1.el7.x86_64
KVM = 2.3.0 - 29.1.el7
libvirt = libvirt-1.2.17-13.el7_2.3
vdsm = vdsm-4.16.30-0.el7
GlusterFS = glusterfs-3.7.8-1.el7
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
2999
days inactive
2999
days old
2 comments
3 participants
participants (3)
-
Nir Soffer -
Ondřej Svoboda -
paf1＠email.cz