Bug #55255
open"ceph iostat" exception!
0%
Description
ceph iostat can not execute correctly but exception!
Files
Updated by liqun zhang about 2 years ago
- File clock.log-20220402 clock.log-20220402 added
when this occurs, clock is not synchronized, and the clock relative log refers to "clock.log-20220402"
Updated by liqun zhang about 2 years ago
// src/test/test_utime.cc
TEST
{
utime_t stamp_delta = utime_t();
vector<utime_t> delta_t;
utime_t ta(1556122013, 0);
utime_t tb(1556122010, 0);
utime_t tc(1556122012, 0);
delta_t.push_back(tb - ta);
for (int i = 0; i < 70; i++)
{
delta_t.push_back(tc - tb);
}
for (auto delta: delta_t)
{
stamp_delta += delta;
//string si = stringify(stamp_delta);
//cout << si << std::endl;
}
while (delta_t.size() > 6)
{
stamp_delta -= delta_t.front();
//string si = stringify(stamp_delta);
//cout << si << std::endl;
delta_t.erase(delta_t.begin());
}
string si = stringify(stamp_delta);
cout << si << std::endl;
ASSERT_EQ(12, stamp_delta);
utime_t t(1556122013, 839991182);
string s = stringify(t);
cout << s << std::endl;
// time zone may vary where unit test is run, so be cirsumspect...
ASSERT_EQ(s.size(), strlen("2019-04-24T11:06:53.839991-0500"));
ASSERT_TRUE(s[26] '-' || s[26] '+');
ASSERT_EQ(s.substr(0, 9), "2019-04-2");
}
[root@z00 build]# ./bin/unittest_utime
Running main() from gmock_main.cc
[==========] Running 4 tests from 1 test suite.
[----------] Global test environment set-up.
[----------] 4 tests from utime_t
[ RUN ] utime_t.localtime
2106-02-07T14:26:10.000000+0800
/root/toy/thinkfs/src/test/test_utime.cc:36: Failure
Expected equality of these values:
12
stamp_delta
Which is: 2106-02-07T14:26:10.000000+0800
[ FAILED ] utime_t.localtime (1 ms)
[ RUN ] utime_t.gmtime
[ OK ] utime_t.gmtime (0 ms)
[ RUN ] utime_t.asctime
[ OK ] utime_t.asctime (0 ms)
[ RUN ] utime_t.parse_date
2019-04-24T16:06:53.039991Z > 2019-04-24T16:06:53.039991Z] 4 tests from utime_t (1 ms total)
2019-04-24 16:06:53.039991Z -> 2019-04-24T16:06:53.039991Z
2019-04-24 16:06:53.039991+0000 -> 2019-04-24T16:06:53.039991Z
2019-04-24 16:06:53.039991-0100 -> 2019-04-24T17:06:53.039991Z
2019-04-24 16:06:53.039991+0430 -> 2019-04-24T11:36:53.039991Z
2019-04-24 16:06:53+0000 -> 2019-04-24T16:06:53.000000Z
2019-04-24T16:06:53-0100 -> 2019-04-24T17:06:53.000000Z
2019-04-24 16:06:53+0430 -> 2019-04-24T11:36:53.000000Z
2019-04-24 -> 2019-04-24T00:00:00.000000Z
[ OK ] utime_t.parse_date (0 ms)
[---------
[----------] Global test environment tear-down
[==========] 4 tests from 1 test suite ran. (1 ms total)
[ PASSED ] 3 tests.
[ FAILED ] 1 test, listed below:
[ FAILED ] utime_t.localtime
1 FAILED TEST
Updated by liqun zhang about 2 years ago
from the test_utime.cc, when stamp_delta overflow, the test is not expected as follows:
Expected equality of these values:
12
stamp_delta
Which is: 2106-02-07T14:26:10.000000+0800
Updated by liqun zhang about 2 years ago
@nojha@redhat.com
@adking@redhat.com
@jdurgin@redhat.com
@kchai@redhat.com
Updated by Radoslaw Zarzynski about 2 years ago
Hello! How do you synchronize the clocks in your cluster? Is NTP properly running?
I'm asking about that to ensure we aren't trying to move the clock synchronization responsibility to Ceph.
Updated by Radoslaw Zarzynski about 2 years ago
- Status changed from New to Need More Info