[LU-10873] Add support for used inode/space on MDT/OST proc Created: 03/Apr/18 Updated: 30/Apr/18 Resolved: 30/Apr/18 |
|
| Status: | Closed |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Minor |
| Reporter: | Qian Yingjin (Inactive) | Assignee: | Qian Yingjin (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
We have a monitoring system which can get the informations from /proc/fs/lustre/osd-*/testfs-OST0000/filesused /proc/fs/lustre/osd-*/testfs-OST0000/kbytesused |
| Comments |
| Comment by Gerrit Updater [ 03/Apr/18 ] |
|
Yingjin Qian (qian@ddn.com) uploaded a new patch: https://review.whamcloud.com/31854 |
| Comment by Andreas Dilger [ 04/Apr/18 ] |
|
The kbytesused and inodesused amounts are just kbytestotal - kbytesfree and inodestotal - inodesfree, so there is no need to export them separately. |
| Comment by Li Xi (Inactive) [ 13/Apr/18 ] |
|
The used capacity/inode can be calculated indeed from total - free. However, mathematical operation is not supported in all monitoring solutions, at least not in the framework that we are currently using. We adding the support, but still, I think other users would still find that they can not get the used capacity/inode easily. And calculating it manually from total and free capacity/inode obviously is not a good experience for administrators. |
| Comment by Li Xi (Inactive) [ 30/Apr/18 ] |
|
This patch is less essential for us (DDN) now, since we've implemented the math support in our monitoring system just a few hours ago. I am going to abandon the patch and close this ticket. Maybe other users of Lustre might found it useful to be able to read used inode/space directly from /proc. If anyone feels necessary, just re-open this ticket. |