Linux XFS filesystem development
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 201973] File Size
Date: Wed, 12 Dec 2018 15:31:59 +0000	[thread overview]
Message-ID: <bug-201973-201763-Quz2hz9ryF@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201973-201763@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=201973

Eric Sandeen (sandeen@sandeen.net) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |sandeen@sandeen.net
         Resolution|---                         |INVALID

--- Comment #1 from Eric Sandeen (sandeen@sandeen.net) ---
Hi, this is the upstream kernel bug tracker, and 3.10.0-862.el7.x86_64 is not
an upstream kernel.  This is not the appropriate bug tracker for distribution
kernels.

Also, you've not provided any reproducer steps, just a screenshot of du & ls
which shows no problem.

There is no expectation that du should match ls.  One reflects the maximum
offset in a file, the other reflects the amount of space allocated to the file.
 They are two different quantities.  Observe:

# fallocate -l 161m output.out
# truncate --size 18g output.out

# du -h output.out
161M    output.out

# ls -lh output.out
-rw-r--r--. 1 root root 18G Dec 12 10:30 output.out

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

      reply	other threads:[~2018-12-12 15:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12  9:28 [Bug 201973] New: File Size bugzilla-daemon
2018-12-12 15:31 ` bugzilla-daemon [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-201973-201763-Quz2hz9ryF@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-xfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox