All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 151491] free space lossage on busy system with bigalloc enabled and 128KB cluster
Date: Mon, 13 Nov 2017 17:30:11 +0000	[thread overview]
Message-ID: <bug-151491-13602-fgTkzlIxfO@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-151491-13602@https.bugzilla.kernel.org/>

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

--- Comment #8 from Betacentauri (betacentauri@arcor.de) ---
Created attachment 260633
  --> https://bugzilla.kernel.org/attachment.cgi?id=260633&action=edit
Test script output

I have used a 4.9 32 bit kernel (config from kernel-configs folder).

Output shows how used space in df command increases. Also files generated by dd
and cp have different file size in ls command.

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

  parent reply	other threads:[~2017-11-13 17:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04 19:47 [Bug 151491] New: free space lossage on busy system with bigalloc enabled and 128KB cluster bugzilla-daemon
2016-08-06 12:54 ` [Bug 151491] " bugzilla-daemon
2016-08-08 20:30 ` bugzilla-daemon
2016-08-09 18:28 ` bugzilla-daemon
2017-11-11 11:04 ` bugzilla-daemon
2017-11-11 19:20 ` bugzilla-daemon
2017-11-13 16:27 ` bugzilla-daemon
2017-11-13 17:27 ` bugzilla-daemon
2017-11-13 17:30 ` bugzilla-daemon [this message]
2017-11-13 17:39 ` bugzilla-daemon
2017-11-16 23:54 ` bugzilla-daemon
2017-11-17 16:00 ` bugzilla-daemon
2017-11-20 15:50 ` bugzilla-daemon
2017-11-20 17:59 ` bugzilla-daemon
2017-11-30 16:08 ` bugzilla-daemon
2017-12-02 11:35 ` bugzilla-daemon
2018-01-27  9:25 ` bugzilla-daemon
2018-01-27 14:20 ` bugzilla-daemon
2018-01-27 19:28 ` bugzilla-daemon
2018-12-03 17:10 ` bugzilla-daemon
2018-12-11 16:44 ` bugzilla-daemon
2018-12-11 18:57 ` bugzilla-daemon
2018-12-13 16:12 ` bugzilla-daemon

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-151491-13602-fgTkzlIxfO@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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.