All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Talpey <tom@talpey.com>
To: kato223@gmail.com, Enzo Matsumiya <ematsumiya@suse.de>,
	CIFS <linux-cifs@vger.kernel.org>
Subject: Re: [Bug 13570] CIFS Mount Used Size descrepancy
Date: Sun, 4 Sep 2022 10:15:37 -0400	[thread overview]
Message-ID: <1ef69bf2-9532-8653-2d21-83beb8e14906@talpey.com> (raw)
In-Reply-To: <f5708177-ff94-c745-a191-4fdba33a2e06@talpey.com>

[resend including linux-cifs]

On 9/4/2022 10:13 AM, Tom Talpey wrote:
> [I don't have a Samba-bugzilla account, so replying directly]
> 
> This is clearly just a TB/TiB discrepancy in reporting.
> 
> 9.1 TB * 10e12 / 2e16 == 8.3 TiB
> 
> Odd that the "Size" and "Avail" numbers are the same, that's maybe
> worth looking into. I bet this is some sort of ancient compatibility
> behavior for a Windows-style API.
> 
> On 9/3/2022 5:55 PM, samba-bugs@samba.org wrote:
>> https://bugzilla.samba.org/show_bug.cgi?id=13570
>>
>> --- Comment #8 from Terrance <kato223@gmail.com> ---
>> Top line is the Samba mounted share and the bottom line is the exact 
>> same share
>> mounted on NFS.
>>
>> Filesystem                 Size  Used Avail Use% Mounted on
>> {..}
>> //10.0.0.220/storage        15T  9.1T  5.5T  63% /media/Samba
>> 10.0.0.220:/media/storage   15T  8.3T  5.5T  61% /media/NAS
>>

  parent reply	other threads:[~2022-09-04 14:15 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 [this message]
2022-09-03 21:56 ` samba-bugs

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=1ef69bf2-9532-8653-2d21-83beb8e14906@talpey.com \
    --to=tom@talpey.com \
    --cc=ematsumiya@suse.de \
    --cc=kato223@gmail.com \
    --cc=linux-cifs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.