From: samba-bugs@samba.org
To: cifs-qa@samba.org
Subject: [Bug 13570] CIFS Mount Used Size descrepancy
Date: Sat, 03 Sep 2022 21:56:45 +0000 [thread overview]
Message-ID: <bug-13570-10630-58Lr0lnlto@https.bugzilla.samba.org/> (raw)
In-Reply-To: <bug-13570-10630@https.bugzilla.samba.org/>
https://bugzilla.samba.org/show_bug.cgi?id=13570
--- Comment #9 from Terrance <kato223@gmail.com> ---
Sorry, NFS share is correct.
terrance@terrance-ubuntu:~$ ssh 10.0.0.220 'df -h'
Filesystem Size Used Avail Use% Mounted on
tmpfs 368M 3.3M 364M 1% /run
/dev/md0 455G 320G 112G 75% /
tmpfs 1.8G 16K 1.8G 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
/dev/md1p1 15T 8.3T 5.5T 61% /media/storage
tmpfs 368M 120K 367M 1% /run/user/1000
--
You are receiving this mail because:
You are the QA Contact for the bug.
prev parent reply other threads:[~2022-09-03 21:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-13570-10630@https.bugzilla.samba.org/>
2020-10-29 14:36 ` [Bug 13570] CIFS Mount Used Size descrepancy samba-bugs
2022-08-19 18:47 ` samba-bugs
2022-08-19 18:51 ` samba-bugs
2022-08-25 14:57 ` samba-bugs
2022-09-03 14:17 ` samba-bugs
2022-09-03 19:22 ` samba-bugs
2022-09-03 21:53 ` samba-bugs
2022-09-03 21:55 ` samba-bugs
[not found] ` <f5708177-ff94-c745-a191-4fdba33a2e06@talpey.com>
2022-09-04 14:15 ` Tom Talpey
2022-09-03 21:56 ` samba-bugs [this message]
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=bug-13570-10630-58Lr0lnlto@https.bugzilla.samba.org/ \
--to=samba-bugs@samba.org \
--cc=cifs-qa@samba.org \
/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