linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andres Freund <andres@anarazel.de>
To: Theodore Tso <tytso@mit.edu>
Cc: adilger@sun.com, LKML <linux-kernel@vger.kernel.org>,
	linux-ext4@vger.kernel.org
Subject: Re: EXT4 ENOSPC Bug
Date: Sat, 29 Nov 2008 22:31:29 +0100	[thread overview]
Message-ID: <200811292231.33799.andres@anarazel.de> (raw)
In-Reply-To: <20081129211533.GG3372@mit.edu>

[-- Attachment #1: Type: text/plain, Size: 631 bytes --]

On Saturday 29 November 2008 22:15:33 Theodore Tso wrote:
> On Sat, Nov 29, 2008 at 02:18:19PM +0100, Andres Freund wrote:
> > On a testsystem (spare laptop) with ext4 as root filesystem sometimes the
> > system starts to return ENOSPC to all write/create syscalls.
> > Sometimes the system runs without problems, at other times it starts
> > having problems soon after boot.
> Hmm.... Is there anything interesting log messages relating to ext4 or
> jbd2 showing up in /var/log/messages or in dmesg?
Nothing else than telling that barriers are not used (I am using dm-crypt...), 
but that shouldnt be related.

Andres

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-11-29 21:31 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 [this message]
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
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=200811292231.33799.andres@anarazel.de \
    --to=andres@anarazel.de \
    --cc=adilger@sun.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).