On Wed, Jan 4, 2012 at 3:48 AM, Daniel Pocock <daniel@xxxxxxxxxxxxx> wrote:
>
>>> I am looking at what metrics are needed to monitor btrfs in production.
>>> I actually look after the ganglia-modules-linux package, which includes
>>> some FS space metrics, but I figured that btrfs throws all that out the
>>> window.
>>>
>>> Can you suggest metrics that would be meaningful, do I look in /proc or
>>> with syscalls, is there any code I should look at for an example of how
>>> to extract them with C? Ideally, Ganglia runs without root privileges
>>> too, so please let me know if btrfs will allow me to access them
>>
>> It depends on what you want to know, really. If you want "how close
>> am I to a full filesystem?", then the output of df will give you a
>> measure, even if it could be up to a factor of 2 out -- you can use it
>> for predictive planning, though, as it'll be near zero when the FS
>> runs out of space.
>
>
> Maybe if you look at it from the point of the sysadmin and think about
> what questions he might want to ask:
>
> a) how much space would I reclaim if I deleted snapshot X?
>
> b) how much space would I reclaim if I deleted all snapshots?
>
> c) how much space would I need if I start making 4 snapshots a day and
> keeping them for 48 hours?
chiming in on the discussion - what I'd like to personally see:
First, probably easiest: Display per subvol the space used that is
"unique" (not used by other subvolumes), and shared (the opposite -
all blocks that appear in other subvolumes as well).
>From there on, one could potentially create a matrix: (proportional
font art, apologies):
| subvol1 | subvol2 | subvol3 |
----------+----------+----------+----------+
subvol1 | 200M | 20M | 50M |
----------+----------+----------+----------+
subvol2 | 20M | 350M | 22M |
----------+----------+----------+----------+
subvol3 | 50M | 22M | 634M |
----------+----------+----------+----------+
The diagonal obviously shows the "unique" blocks, subvol2 and subvol1
share 20M data, etc. Missing from this plot would be "how much is
shared between subvol1, subvol2, and subvol3" together, but it's a
start and not something that hard to understand. One might add a
column for "total size" of each subvol, which may obviously not be an
addition of the rest of the columns in this diagram.
Anyway, something like this would be high on my list of `df` numbers
I'd like to see - since I think they are useful numbers.
Cheers,
Auke
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
