From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 15768] New: Incorrectly calculated free blocks result in ENOSPC from writepage
Date: Mon, 12 Apr 2010 11:26:24 GMT [thread overview]
Message-ID: <bug-15768-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=15768
Summary: Incorrectly calculated free blocks result in ENOSPC
from writepage
Product: File System
Version: 2.5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: dmonakhov@openvz.org
CC: tytso@mit.edu
Regression: No
Created an attachment (id=25965)
--> (https://bugzilla.kernel.org/attachment.cgi?id=25965)
testcase
No mount per-sb counters (freeblocks/freeinodes/dir and etc) are initialized
before journal was replayed.
But in fact if journal wasn't empty statistics will be probably changed after
journal replay. This result in per-sb counter inconsistency which result in
incorrect delalloc reservation. See testcase.
This is long standing bug at least from 2.6.12 where the linus's tree starts i
(was too lazy to dig in to old-git tree).
But it case of ext3 this result only in incorrect numbers from statfs()
The fix is simple, we just have to move counter initialisation after
journal_reply.
I've open this bug only as testcase storage.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2010-04-12 11:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 11:26 bugzilla-daemon [this message]
2010-04-12 11:32 ` [Bug 15768] Incorrectly calculated free blocks result in ENOSPC from writepage bugzilla-daemon
2010-04-12 11:50 ` bugzilla-daemon
2010-04-12 18:30 ` bugzilla-daemon
2010-04-12 19:14 ` bugzilla-daemon
2010-04-16 21:44 ` bugzilla-daemon
2010-05-04 21:15 ` bugzilla-daemon
2010-06-13 11:44 ` 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-15768-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).