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, 20 Nov 2017 15:50:09 +0000 [thread overview]
Message-ID: <bug-151491-13602-4iiHF8y1RA@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 #12 from Eric Whitney (enwlinux@gmail.com) ---
After many attempts, I'm unable to reproduce the newly reported behavior for
the delalloc workaround in comment 11 on my x86-64 test system (which is not an
xfstests-bld test appliance) running either a current 4.14 kernel or an older
Debian Jessie 4.8 kernel. I consistently get a reported value of 10240 1k
units, which is correct for the reported size.
However, in the process of running my trials I arrived at a simpler reproducer
that should be helpful in identifying the source of the original space
reporting problem. There's no need to copy the first test file if the test
system's free memory is sufficiently limited relative to the size of the test
file - a simple sequential write of a single test file suffices. In fact, the
tighter the free memory, the more likely the problem occurs and the likelihood
of larger reporting errors increases. A test system with ample free memory
won't exhibit the problem at all.
I'm getting workable kernel traces with the simpler reproducer, and the free
memory-related behavior suggests a direction, so I'll see where that takes me.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2017-11-20 15:50 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
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 [this message]
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-4iiHF8y1RA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox