From: Theodore Tso <tytso@mit.edu>
To: Andres Freund <andres@anarazel.de>
Cc: adilger@sun.com, LKML <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org,
Jonathan Bastien-Filiatrault <joe@x2a.org>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: EXT4 ENOSPC Bug
Date: Mon, 16 Feb 2009 10:01:56 -0500 [thread overview]
Message-ID: <20090216150156.GD22619@mini-me.lan> (raw)
In-Reply-To: <49994FEF.2020908@anarazel.de>
On Mon, Feb 16, 2009 at 12:37:19PM +0100, Andres Freund wrote:
> Hi All,
>
> "Luckily", to prove that I am not completly mad I recently found this
> problem again. On a more recent kernel:
> 2.6.29-rc3-andres-00498-g68e80d5
> (upstream 2.6.29 + Theodore's ext4 debug patches)
>
> Again I got:
> open("/home/andres/tt", O_WRONLY|O_CREAT|O_NOCTTY|O_NONBLOCK, 0666) = -1
> ENOSPC (No space left on device)
So /home/andres/tt does not exist, correct? Does this happen for any
attempt to create a new zero-length file using the "touch" command?
(Even in other directories) Can you append to a file using "cat
/etc/mailcap >> some_existing_file"?
If it is "yes" to the first two questions, and "no" the third, it
looks like this might be an inode allocation failure as opposed to a
block allocation failure.
Once this triggers, does it reliably continue to fail if you reboot?
Or does it go away when you reboot?
- Ted
next prev parent reply other threads:[~2009-02-16 15:20 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 13:18 EXT4 ENOSPC Bug Andres Freund
2008-11-29 20:32 ` Jonathan Bastien-Filiatrault
2008-11-29 21:15 ` Theodore Tso
2008-11-29 21:31 ` Andres Freund
2008-12-01 12:34 ` Andres Freund
2008-12-01 19:42 ` Andreas Dilger
2008-12-01 20:16 ` Andres Freund
2008-12-02 7:57 ` Theodore Tso
2008-12-02 14:58 ` Andres Freund
2008-12-02 16:47 ` Theodore Tso
2008-12-02 17:47 ` Andres Freund
2008-12-02 20:33 ` Theodore Tso
2008-12-03 0:37 ` Jonathan Bastien-Filiatrault
2008-12-03 0:40 ` Jonathan Bastien-Filiatrault
2008-12-03 4:37 ` Theodore Tso
2008-12-03 15:34 ` Aneesh Kumar K.V
2008-12-03 17:23 ` Theodore Tso
2008-12-03 18:18 ` Andres Freund
2008-12-02 15:26 ` Henrique de Moraes Holschuh
2008-12-10 0:07 ` Andres Freund
2009-02-16 11:37 ` Andres Freund
2009-02-16 15:01 ` Theodore Tso [this message]
2009-02-16 15:27 ` Andres Freund
2009-02-16 19:00 ` Theodore Tso
2009-02-17 17:21 ` Alex Buell
2009-02-17 17:36 ` Andres Freund
2009-02-18 21:18 ` Andres Freund
2009-02-18 21:29 ` Theodore Tso
2009-02-19 2:18 ` Andres Freund
2009-02-19 3:22 ` Theodore Tso
2009-02-19 15:46 ` Eric Sandeen
2009-02-23 2:02 ` Theodore Tso
2009-02-27 3:57 ` Andres Freund
2009-02-17 18:13 ` Eric Sandeen
2009-02-17 20:08 ` Eric Sandeen
[not found] ` <499B1935.10906@redhat.com>
2009-02-17 22:00 ` Theodore Tso
2009-02-17 22:30 ` Alex Buell
2009-02-17 22:56 ` Eric Sandeen
2009-02-17 22:59 ` Alex Buell
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=20090216150156.GD22619@mini-me.lan \
--to=tytso@mit.edu \
--cc=adilger@sun.com \
--cc=andres@anarazel.de \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=joe@x2a.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@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).