On 2016-05-16 08:14, Richard W.M. Jones wrote:
I don't have time to implement this right now, so I'm just posting
this as a suggestion/request ...
It would be really helpful if the btrfs tools had a machine-readable
output.
Libguestfs parses btrfs tools output in a number of places, eg:
https://github.com/libguestfs/libguestfs/blob/master/daemon/btrfs.c
This is a massive PITA because each time a new release of btrfs-progs
comes along it changes the output slightly, and we end up having
to add all sorts of hacks.
With machine-readable output, there'd be a flag which would
change the output. eg:
$ btrfs filesystem show
Label: 'ROOT' uuid: af471cfc-421a-4d51-8811-ce969f76828a
Total devices 1 FS bytes used 5.29MiB
devid 1 size 767.97MiB used 92.00MiB path /dev/sda2
would become:
$ btrfs --json filesystem show
{
"devices": {
"Label": "ROOT",
"uuid": "af471cfc-421a-4d51-8811-ce969f76828a",
/// etc
}
}
By this example I don't mean that JSON has to be the format -- in fact
it's a terrible format with all sorts of problems -- any format which
is parseable with C libraries would do for us.
I would love to see something like this myself, as it would make
integration with monitoring tools so much easier. I'd vote for YAML as
the output format though, as it's easily human readable as well as
machine parseable while still being space efficient. Output from your
example above might look something like this:
---
- filesystems
- label: 'ROOT'
uuid: af471cfc-421a-4d51-8811-ce969f76828a
devices: 1
- devid: 1
size: 767.97 MB
used 92.00 MB
path: /dev/sda2
used: 5.29 MB
...
Although of course the numbers would probably just be in bytes instead
of 'human' values.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
