From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12829] kernel complains on ENOSPC
Date: Fri, 6 Mar 2009 15:02:21 -0800 (PST) [thread overview]
Message-ID: <20090306230222.2732110800D@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-12829-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=12829
------- Comment #1 from tytso@mit.edu 2009-03-06 15:02 -------
What are the precise reproduction details? We're supposed to keep track of
how many delayed allocation blocks are outstanding, so that we return ENOSPC
*before* we get to this stage.
I'm not sure we do the right thing if we mmap into an unallocated region of
file; when do we actually track delayed allocation blocks? The right answer
would be at mmap() time, but OTOH that means if we mmap a 2GB region, do we
immediately take a 2GB charge because the process might write into this region?
And does free space returned by 'df' immediately drop by 2GB?
Do you know if there was any allocation by mmap going on in your reproduction
case? That seems the most likely cause to me, if I had to guess....
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2009-03-06 23:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 22:33 [Bug 12829] New: kernel complains on ENOSPC bugme-daemon
2009-03-06 23:02 ` bugme-daemon [this message]
2009-03-09 5:16 ` [Bug 12829] " Aneesh Kumar K.V
2009-03-06 23:28 ` bugme-daemon
2009-03-09 5:17 ` bugme-daemon
2009-03-10 16:38 ` bugme-daemon
2009-04-06 18:58 ` Theodore Tso
2009-04-07 14:31 ` Aneesh Kumar K.V
2009-04-07 16:15 ` Theodore Tso
2009-05-19 19:24 ` bugzilla-daemon
2010-03-15 20:23 ` bugzilla-daemon
[not found] <bug-12829-13602@https.bugzilla.kernel.org/>
2012-05-30 14:33 ` bugzilla-daemon
2012-05-30 14:33 ` 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=20090306230222.2732110800D@picon.linux-foundation.org \
--to=bugme-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).