[SERVER-28953] Capture df (disk full) statistics in FTDC Created: 25/Apr/17 Updated: 30/Oct/23 Resolved: 09/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0, 5.0.6, 4.4.11, 4.2.18 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Henrik Ingo (Inactive) | Assignee: | Sergey Galtsev (Inactive) |
| Resolution: | Fixed | Votes: | 5 |
| Labels: | SWDI, move-sec, platforms-re-triaged | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||||||||||
| Backport Requested: |
v5.0, v4.4, v4.2, v4.0
|
||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Security 2021-11-01, Security 2021-11-15 | ||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
As we now collect also system metrics in the diagnostic data, it would be sometimes useful to know how full a disk was (or, in particular, whether it was 100% full). Edit (JamesB): this would be most useful as <bytes available> / <bytes total>, not a percentage |
| Comments |
| Comment by Githook User [ 01/Dec/21 ] | |||||
|
Author: {'name': 'sergey.galtsev', 'email': 'sergey.galtsev@mongodb.com', 'username': 'brushless-glitch'}Message: | |||||
| Comment by Githook User [ 01/Dec/21 ] | |||||
|
Author: {'name': 'sergey.galtsev', 'email': 'sergey.galtsev@mongodb.com', 'username': 'brushless-glitch'}Message: | |||||
| Comment by Githook User [ 01/Dec/21 ] | |||||
|
Author: {'name': 'sergey.galtsev', 'email': 'sergey.galtsev@mongodb.com', 'username': 'brushless-glitch'}Message: | |||||
| Comment by Githook User [ 08/Nov/21 ] | |||||
|
Author: {'name': 'sergey.galtsev', 'email': 'sergey.galtsev@mongodb.com', 'username': 'brushless-glitch'}Message: | |||||
| Comment by Alex Bevilacqua [ 22/Oct/21 ] | |||||
|
sergey.galtsev I see that as well. My apologies, I assumed OSX was capturing the same telemetry as Linux. in this case I guess Linux for sure, Windows if possible. | |||||
| Comment by Sergey Galtsev (Inactive) [ 21/Oct/21 ] | |||||
| |||||
| Comment by Sergey Galtsev (Inactive) [ 21/Oct/21 ] | |||||
|
alex.bevilacqua can you please confirm that OSX requirement? I did a quick verification, and I don't see that OSX version currently collects disk information at all. | |||||
| Comment by Alex Bevilacqua [ 21/Oct/21 ] | |||||
|
sergey.galtsev this should be available on all platforms if possible, but OSX/Linux for sure. | |||||
| Comment by Sergey Galtsev (Inactive) [ 21/Oct/21 ] | |||||
|
renato.riccio can you clarify whether this feature should be limited to Linux, available on all platforms, or up to discretion? | |||||
| Comment by Bruce Lucas (Inactive) [ 20/Jul/17 ] | |||||
I would suggest capturing both bytes used (not bytes available) and bytes total. That way we can see whether percent usage changed because disk usage changed or because disk capacity changed. Bytes used is better than bytes available because it won't change when capacity changes, whereas bytes available will. | |||||
| Comment by Henrik Ingo (Inactive) [ 02/May/17 ] | |||||
|
Expanding on Bruce's list:
| |||||
| Comment by Bruce Lucas (Inactive) [ 28/Apr/17 ] | |||||
|
From a diagnostic perspective, normally you would expect to be able to learn that a failure was caused by running out of disk space from mongod logs. However I can think of two circumstances where having this information in FTDC as well would be useful:
| |||||
| Comment by Henrik Ingo (Inactive) [ 26/Apr/17 ] | |||||
|
The concrete issue I've linked is weird things happening, that may or may not have been caused because a disk was full. (Note that we can of course run df ourselves when testing, but I wanted to propose this from a completeness point of view. Since ftdc data obsolotes the need to run iostat, why not df too?) I guess from a support point of view, additional value could be provided if we could tell the customer: "By the way, your disk is 95% full and will be completely full in a month from now." | |||||
| Comment by Mark Benvenuto [ 25/Apr/17 ] | |||||
|
Are you worried about the effects of file allocation getting slower as disk fills up? Or just it hitting 100%? Linux: statfs (2) Cc: bruce.lucas |