df.exe does not report status of network filesystems like SMB, NFSv3, NFSv4.2 (ms-nfs41-client), CephFS, ...

Open
#82 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust

Research direction

Start at the df.exe entry point and reproduce the issue with the listed SMB, NFS, and CephFS network filesystems. Trace how filesystem status is enumerated on Windows, then verify that network mounts report filesystem, capacity, usage, and mount-point data like the Cygwin and MSYS2 examples; the issue names no test file.

Written by the indexing model from the issue text.

Description

C-bug

df.exe does not report status of network filesystems like SMB, NFSv3, NFSv4.2 (ms-nfs41-client), CephFS, ...

$ df.exe
Filesystem 1K-blocks Used Available Use% Mounted on
\?\Volume{f6d90251-0739-4aa9-a981-408113eb268c}\ 401980180 270931472 131048708 68% C:
\?\Volume{9f160871-d1b8-11ef-8c9b-806e6w6e6963}\ 6010038 6010038 0 100% D:\

Cygwin and MSYS2 df.exe eport all filesystems:
$ df -k
Filesystem 1K-blocks Used Available Use% Mounted on
C:/cygwin64 401980180 270931584 131048596 68% /
H: 1953514584 1774552848 175195264 92% /cygdrive/h
D: 6010038 6010038 0 100% /cygdrive/d
E: 31997344 2723256 29274088 9% /cygdrive/e
F: 123869696 45786728 78082968 37% /cygdrive/f
I: 1953514584 1774552848 175195264 92% /cygdrive/i
J: 500107608 303016512 182767216 63% /cygdrive/j
L: 500107608 303016512 182767216 63% /cygdrive/l
M: 500107608 303016512 182767216 63% /cygdrive/m
O: 500107608 303016512 182767216 63% /cygdrive/o
P: 500107608 303016512 182767216 63% /cygdrive/p
R: 436336 0 436336 0% /cygdrive/r
T: 436336 0 436336 0% /cygdrive/t

Dominant language
Rust
Stars
5.2k
Forks
107
Avg merge
2d 19h
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/coreutils

All issues in microsoft/coreutils

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.