From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>
Cc: pbs-devel@lists.proxmox.com
Subject: Re: [pbs-devel] [PATCH proxmox v3 2/3] proxmox-sys: add FileSystemInformation struct and helper
Date: Wed, 12 Jan 2022 15:10:35 +0100 [thread overview]
Message-ID: <20220112141035.3rtm4z4isqd6tqs7@olga.proxmox.com> (raw)
In-Reply-To: <20211217081000.1061796-3-d.csapak@proxmox.com>
minor nit...
On Fri, Dec 17, 2021 at 09:09:53AM +0100, Dominik Csapak wrote:
> code mostly copied from proxmox-backups 'disk_usage'
>
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> proxmox-sys/src/fs/mod.rs | 39 +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 39 insertions(+)
>
> diff --git a/proxmox-sys/src/fs/mod.rs b/proxmox-sys/src/fs/mod.rs
> index 9fe333b..f8a7744 100644
> --- a/proxmox-sys/src/fs/mod.rs
> +++ b/proxmox-sys/src/fs/mod.rs
> @@ -102,3 +102,42 @@ impl CreateOptions {
> */
> }
>
> +/// Information about a mounted file system from statfs64 syscall
> +pub struct FileSystemInformation {
> + /// total bytes available
> + pub total: u64,
> + /// bytes used
> + pub used: u64,
> + /// bytes available to an unprivileged user
> + pub available: u64,
> + /// total number of inodes
> + pub total_inodes: u64,
> + /// free number of inodes
> + pub free_inodes: u64,
> + /// the type of the filesystem (see statfs64(2))
> + pub fs_type: i64,
> + /// the filesystem id
> + pub fs_id: libc::fsid_t,
> +}
> +
> +/// Get file system information from path
> +pub fn fs_info(path: &std::path::Path) -> Result<FileSystemInformation, Error> {
If you use `NixPath` below anyway, may as well go all the way:
pub fn fs_info<P: ?Sized + NixPath>(path: &P) -> nix::Result<FileSystemInformation> {
(note the error type change since that's the only kind of error
appearing in this function)
Otherwise, you could at least go the `std` way of `<P: AsRef<Path>>(path: P)`.
(We're already mixing these a bit, but `&Path` is the least convenient
way for callers to interact with)
> + let mut stat: libc::statfs64 = unsafe { std::mem::zeroed() };
> +
> + use nix::NixPath;
> +
> + let res = path.with_nix_path(|cstr| unsafe { libc::statfs64(cstr.as_ptr(), &mut stat) })?;
> + nix::errno::Errno::result(res)?;
> +
> + let bsize = stat.f_bsize as u64;
> +
> + Ok(FileSystemInformation {
> + total: stat.f_blocks * bsize,
> + used: (stat.f_blocks - stat.f_bfree) * bsize,
> + available: stat.f_bavail * bsize,
> + total_inodes: stat.f_files,
> + free_inodes: stat.f_ffree,
> + fs_type: stat.f_type,
> + fs_id: stat.f_fsid,
> + })
> +}
> --
> 2.30.2
next prev parent reply other threads:[~2022-01-12 14:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 8:09 [pbs-devel] [PATCH proxmox/proxmox-backup v3] add metrics server capability Dominik Csapak
2021-12-17 8:09 ` [pbs-devel] [PATCH proxmox v3 1/3] proxmox-sys: make some structs serializable Dominik Csapak
2021-12-17 8:09 ` [pbs-devel] [PATCH proxmox v3 2/3] proxmox-sys: add FileSystemInformation struct and helper Dominik Csapak
2022-01-12 14:10 ` Wolfgang Bumiller [this message]
2021-12-17 8:09 ` [pbs-devel] [PATCH proxmox v3 3/3] proxmox-metrics: implement metrics server client code Dominik Csapak
2022-01-12 14:36 ` Wolfgang Bumiller
2021-12-17 8:09 ` [pbs-devel] [PATCH proxmox-backup v3 1/6] use 'fs_info' from proxmox-sys Dominik Csapak
2021-12-17 8:09 ` [pbs-devel] [PATCH proxmox-backup v3 2/6] pbs-api-types: add metrics api types Dominik Csapak
2022-01-12 14:40 ` Wolfgang Bumiller
2021-12-17 8:09 ` [pbs-devel] [PATCH proxmox-backup v3 3/6] pbs-config: add metrics config class Dominik Csapak
2021-12-17 8:09 ` [pbs-devel] [PATCH proxmox-backup v3 4/6] backup-proxy: decouple stats gathering from rrd update Dominik Csapak
2021-12-17 8:09 ` [pbs-devel] [PATCH proxmox-backup v3 5/6] proxmox-backup-proxy: send metrics to configured metrics server Dominik Csapak
2021-12-17 8:10 ` [pbs-devel] [PATCH proxmox-backup v3 6/6] api: add metricserver endpoints Dominik Csapak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220112141035.3rtm4z4isqd6tqs7@olga.proxmox.com \
--to=w.bumiller@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox