mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Andreas Dilger <adilger@sun.com>
Cc: Andres Freund <andres@anarazel.de>, Theodore Tso <tytso@mit.edu>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-ext4@vger.kernel.org
Subject: Re: EXT4 ENOSPC Bug
Date: Tue, 2 Dec 2008 13:26:56 -0200	[thread overview]
Message-ID: <20081202152656.GH1668@khazad-dum.debian.net> (raw)
In-Reply-To: <20081201194204.GZ3186@webber.adilger.int>

On Mon, 01 Dec 2008, Andreas Dilger wrote:
> - do the applications writing to this file have any unusual IO pattern
>   (e.g. mmap IO, lots of write+truncate+write on the same file, etc)

Vuze does a massive ammount of sparse writes.  It can also be configured to
pre-allocate space (either by creating an empty non-sparse file, or by
telling the kernel that the file is expected to grow to size foo and to
please pre-allocate that in the filesystem.  I don't recall how this is
done).

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  parent reply	other threads:[~2008-12-02 15:27 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090216162028.3032666a@lithium.local.net>
2008-11-29 13:18 ` 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 [this message]
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
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=20081202152656.GH1668@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=adilger@sun.com \
    --cc=andres@anarazel.de \
    --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

all inboxes | Powered by JetHome®