display free/used inodes
daniejstriata opened this issue · 17 comments
Can you please add option to add a column for free/used inodes?
In the JSON output, why not, but is this a so frequent concern that you'd also want it in the table view ?
only Display inodes column if I ask for it?
I run lfs as part of my motd. It would be good for me to show inodes issues to admins logging in,
I'll probably do it, as it's quite easy
Not 100% sure about the presentation but I might settle for this:
I've also tested with % but it doesn't really help IMO:
There are other ways to get the exact inodes total and used. I'd be happy just to see the percentage of inodes in use.
You mean your opinion would be to choose just "free inodes" and "inodes use%" ?
Yes. I've never worried about inodes until there are none left :-) I actually ran into an XFS volume today that started complaining about inodes. I've not seen xfs having inode issues before.
As you can see, it's not really my current concern:
In a future versions, I'll probably make it possible to finely decide what cols to display...
(depending on whether I have another user or not ^^)
That example looks great. I would even drop the free inodes column.
Choosing column in future could be helpful. Maybe have a "lite" and "full" option?
full:
┌───┬─────┬─────────────────────────────────┬────┬────┬────┬─────────┬────┬────┬───────────┐
│ id│ dev │ filesystem │disk│type│used│ use% │free│size│mount point│
├───┼─────┼─────────────────────────────────┼────┼────┼────┼─────────┼────┼────┼───────────┤
│150│253:1│/dev/mapper/root │LVM │xfs │26G │59% ███ │ 18G│44G │/ │
│112│253:1│/dev/mapper/root │LVM │xfs │26G │59% ███ │ 18G│44G │/var/tmp │
│169│253:3│/dev/mapper/home │LVM │xfs │14G │66% ███▎ │7.4G│21G │/home │
│166│252:1│/dev/vda1 │HDD │ext4│287M│28% █▍ │736M│1.0G│/boot │
└───┴─────┴─────────────────────────────────┴────┴────┴────┴─────────┴────┴────┴───────────┘
lite:
┌─────────────────────────────────┬────┬────┬─────────┬────┬────┬───────────┐
│ filesystem │type│used│ use% │free│size│mount point│
├─────────────────────────────────┼────┼────┼─────────┼────┼────┼───────────┤
│/dev/mapper/root │xfs │26G │59% ███ │ 18G│44G │/ │
│/dev/mapper/root │ │26G │59% ███ │ 18G│44G │/var/tmp │
│/dev/mapper/home │xfs │14G │66% ███▎ │7.4G│21G │/home │
│/dev/vda1 │ext4│287M│28% █▍ │736M│1.0G│/boot │
└─────────────────────────────────┴────┴────┴─────────┴────┴────┴───────────┘
Let's see:
That looks good. What if you add the new inodes column after the use%
I don't want to mix parts in bytes and parts in inodes, that would be ambiguous
I'll go with this for now (testing with a fs without inode):
Released. I've spent more time than expected on the tests and small details...
I appreciate! Thank you.