Is there an equivalent command to QNX4’s fsysinfo?
- Mario
Is there an equivalent command to QNX4’s fsysinfo?
Mario Charest wrote:
Is there an equivalent command to QNX4’s fsysinfo?
Not as a utility, but you can query the information yourself; refer
<sys/fs_stats.h> and DCMD_FSYS_STATISTICS devctl.
“John Garvey” <jgarvey@qnx.com> wrote in message
news:e28ci2$a8l$1@inn.qnx.com…
Mario Charest wrote:
Is there an equivalent command to QNX4’s fsysinfo?Not as a utility, but you can query the information yourself; refer
sys/fs_stats.h> and DCMD_FSYS_STATISTICS devctl.
Thanks for the tip. Ended up writing my own fsysinfo QNX4 lookalike program
“Mario Charest” postmaster@127.0.0.1 wrote in message
news:e28mkl$grk$1@inn.qnx.com…
“John Garvey” <> jgarvey@qnx.com> > wrote in message
news:e28ci2$a8l$> 1@inn.qnx.com> …
Mario Charest wrote:
Is there an equivalent command to QNX4’s fsysinfo?Not as a utility, but you can query the information yourself; refer
sys/fs_stats.h> and DCMD_FSYS_STATISTICS devctl.Thanks for the tip. Ended up writing my own fsysinfo QNX4 lookalike
program >
The documentation for fstatvfs states that f_files f_ffree and f_favail
might not be valid for NFS mounted filesystem, yet qnx4 filesystem these
values are all 0?
- Mario
Mario Charest wrote:
The documentation for fstatvfs states that f_files f_ffree and f_favail
might not be valid for NFS mounted filesystem, yet qnx4 filesystem these
values are all 0?
Since the fs-qnx4 embeds inodes where possible, rather than placing
each in the .inodes, there is no real maximum for this (theorectically
I think it would be 2^28 perhaps, or bounded by disk space?), and
f_files are not counted. So these will all be 0 for fs-qnx4 (and by
similarly argument, fs-dos and fs-cd too) filesystems.
“John Garvey” <jgarvey@qnx.com> wrote in message
news:e2avmu$41q$1@inn.qnx.com…
Mario Charest wrote:
The documentation for fstatvfs states that f_files f_ffree and f_favail
might not be valid for NFS mounted filesystem, yet qnx4 filesystem these
values are all 0?Since the fs-qnx4 embeds inodes where possible, rather than placing
each in the .inodes, there is no real maximum for this (theorectically
I think it would be 2^28 perhaps, or bounded by disk space?), and
f_files are not counted. So these will all be 0 for fs-qnx4 (and by
similarly argument, fs-dos and fs-cd too) filesystems.
Since the doc already mention NFS, would be nice to have the same warning
about all the filesystem where this situation arises.
Cheers,
Mario
Mario Charest postmaster@127.0.0.1 wrote:
Since the doc already mention NFS, would be nice to have the same warning
about all the filesystem where this situation arises.
I’ve create a PR. Thanks for the suggestion.
“Steve Reid” <stever@stevernto.ott.qnx.com> wrote in message
news:e2bfpf$dt8$1@inn.qnx.com…
Mario Charest postmaster@127.0.0.1 wrote:
Since the doc already mention NFS, would be nice to have the same warning
about all the filesystem where this situation arises.I’ve create a PR. Thanks for the suggestion.
Well, thank YOU for watching
Steve Reid > stever@qnx.com
Technical Editor
QNX Software Systems
Mario Charest postmaster@127.0.0.1 wrote:
“Steve Reid” <> stever@stevernto.ott.qnx.com> > wrote in message
news:e2bfpf$dt8$> 1@inn.qnx.com> …
Mario Charest postmaster@127.0.0.1 wrote:
Since the doc already mention NFS, would be nice to have the same warning
about all the filesystem where this situation arises.I’ve create a PR. Thanks for the suggestion.
Well, thank YOU for watching >
You’re welcome. I should also create a PR against myself for forgetting
the “d” on “created” above.