Bug 1680052
| Summary: | "INFO libstratis::engine::strat_engine::thinpool::thinpool:" messages are noisy | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Corey Marthaler <cmarthal> |
| Component: | stratisd | Assignee: | mulhern <amulhern> |
| Status: | CLOSED ERRATA | QA Contact: | guazhang <guazhang> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.0 | CC: | amulhern, dkeefe |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | 8.2 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 1.0.6 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-04-28 15:41:56 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Corey Marthaler
2019-02-22 15:57:16 UTC
Also, the messages don't indicate which pool they're referring to. I have 5 pools/fs, so the messages aren't descriptive enough to be helpful in this scenario. [root@hayes-01 ~]# stratis fs list Pool Name Name Used Created Device UUID my_pool100 fs1 64.68 GiB Feb 21 2019 14:10 /stratis/my_pool100/fs1 d9fbf3d0e9c44e69bc33e69862efa655 my_pool2 fs2 27.55 GiB Feb 21 2019 16:02 /stratis/my_pool2/fs2 041acd0d91bd4fa79bf10457b6369c24 my_pool3 fs2 545 MiB Feb 21 2019 16:04 /stratis/my_pool3/fs2 092e282222244aa0bce3c6b1a56e20e0 my_pool4 fs2 546 MiB Feb 21 2019 16:04 /stratis/my_pool4/fs2 7a10d4f7b3b24d4aadc65cd8bb5612f2 my_pool5 fs2 545 MiB Feb 21 2019 16:13 /stratis/my_pool5/fs2 a9606e209a2b4963b3092fc3bc8c7018 [root@hayes-01 ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/stratis-1-3354bab7fa444f1294b7fd807127781c-thin-fs-d9fbf3d0e9c44e69bc33e69862efa655 1.0T 67G 958G 7% /mnt/stratis1 /dev/mapper/stratis-1-14b9879b40c2497187b0c76c446804d0-thin-fs-041acd0d91bd4fa79bf10457b6369c24 1.0T 33G 992G 4% /mnt/stratis2 /dev/mapper/stratis-1-8d7300e29a4c46048b00e059efe3a2e3-thin-fs-092e282222244aa0bce3c6b1a56e20e0 1.0T 7.2G 1017G 1% /mnt/stratis3 /dev/mapper/stratis-1-d76c5196f2e8492092a48ef2e2ed89ff-thin-fs-7a10d4f7b3b24d4aadc65cd8bb5612f2 1.0T 7.2G 1017G 1% /mnt/stratis4 /dev/mapper/stratis-1-36a22ef6d12347dfb0d58590e0a19de4-thin-fs-a9606e209a2b4963b3092fc3bc8c7018 1.0T 7.2G 1017G 1% /mnt/stratis5 [...] Feb 22 09:44:21 hayes-01 stratisd[970]: INFO libstratis::engine::strat_engine::thinpool::thinpool: Data tier percent used: 3 Feb 22 09:45:01 hayes-01 stratisd[970]: INFO libstratis::engine::strat_engine::thinpool::thinpool: Data tier percent used: 3 Feb 22 09:45:42 hayes-01 stratisd[970]: INFO libstratis::engine::strat_engine::thinpool::thinpool: Data tier percent used: 4 Feb 22 09:46:16 hayes-01 stratisd[970]: INFO libstratis::engine::strat_engine::thinpool::thinpool: Data tier percent used: 4 Feb 22 09:46:52 hayes-01 stratisd[970]: INFO libstratis::engine::strat_engine::thinpool::thinpool: Data tier percent used: 4 Feb 22 09:47:30 hayes-01 stratisd[970]: INFO libstratis::engine::strat_engine::thinpool::thinpool: Data tier percent used: 4 Feb 22 10:07:50 hayes-01 stratisd[2677]: INFO libstratis::engine::strat_engine::thinpool::thinpool: Data tier percent used: 1 Feb 22 10:07:50 hayes-01 stratisd[2677]: INFO libstratis::engine::strat_engine::thinpool::thinpool: Data tier percent used: 4 Feb 22 10:07:51 hayes-01 stratisd[2677]: INFO libstratis::engine::strat_engine::thinpool::thinpool: Data tier percent used: 1 Feb 22 10:07:51 hayes-01 stratisd[2677]: INFO libstratis::engine::strat_engine::thinpool::thinpool: Data tier percent used: 1 Feb 22 10:07:51 hayes-01 stratisd[2677]: INFO libstratis::engine::strat_engine::thinpool::thinpool: Data tier percent used: 1 Feb 22 10:07:52 hayes-01 stratisd[2677]: INFO libstratis::engine::strat_engine::thinpool::thinpool: Data tier percent used: 1 Feb 22 10:07:52 hayes-01 stratisd[2677]: INFO libstratis::engine::strat_engine::thinpool::thinpool: Data tier percent used: 1 Some notes: * That INFO level message is more appropriately a DEBUG level message. We can make it so. * All messages should give the information that is readily and cheaply available at the point that they are generated. This one is probably giving less than that and that could be improved. * There is also a suggested enhancement to the CLI. This is sort of orthogonal. I don't believe that the data tier percent is derived directly from the values displayed in the CLI. We could consider enhancing the table display in the CLI to show percentage proportions. But we might want to consider displaying proportions, by whatever means, including percentages, as an optional thing, rather than the default. The table may be enhanced with other values and the percentages interposed at various places might become awkward clutter. Note that we can anticipate possible putting some additional information in the structured format, that which is not intended to be human readable where formatting issues are less troublesome. See upstream issue: https://github.com/stratis-storage/stratis-cli/issues/292 Mass migration to Guangwu. Hello
test passed with fixed version.
#stratis pool create pool{1..5} /dev/sd{b..f}
# stratis pool list
Name Total Physical
pool1 5.46 TiB / 53.77 MiB / 5.46 TiB
pool2 5.46 TiB / 53.77 MiB / 5.46 TiB
pool3 5.46 TiB / 53.77 MiB / 5.46 TiB
pool4 5.46 TiB / 53.77 MiB / 5.46 TiB
pool5 5.46 TiB / 53.77 MiB / 5.46 TiB
#stratis filesystem create pool{1..5} fs{1..5}
# stratis fs list
Pool Name Name Used Created Device UUID
pool1 fs1 546 MiB Nov 25 2019 05:04 /stratis/pool1/fs1 117bf9f2ed304dfa8394d612c666e640
pool2 fs2 546 MiB Nov 25 2019 05:04 /stratis/pool2/fs2 c123a465fc0e4fdbb8d6a8580f487553
pool3 fs3 546 MiB Nov 25 2019 05:04 /stratis/pool3/fs3 fe66f98098ee46ffb979fae8d4c4297c
pool4 fs4 546 MiB Nov 25 2019 05:04 /stratis/pool4/fs4 4b68305a98674c508ed2072460bbd19a
pool5 fs5 546 MiB Nov 25 2019 05:04 /stratis/pool5/fs5 1fdee08cc4724df68081b66c1f1eff99
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:1634 |