All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Manas Garg <mls@chakpak.net>, linux-kernel@vger.kernel.org
Subject: Re: O_TRUNC problem on a full filesystem
Date: Thu, 24 May 2001 21:28:40 +1000	[thread overview]
Message-ID: <3B0CF068.A6ADA562@uow.edu.au> (raw)
In-Reply-To: <20010523114318.A8336@cygsoft.com> <3B0B8924.F0B78288@uow.edu.au>, <3B0B8924.F0B78288@uow.edu.au>; from andrewm@uow.edu.au on Wed, May 23, 2001 at 07:55:48PM +1000 <20010524121634.O8080@redhat.com>

"Stephen C. Tweedie" wrote:
> 
> On Wed, May 23, 2001 at 07:55:48PM +1000, Andrew Morton wrote:
> 
> > When you truncated your file, the blocks remained preallocated
> > on behalf of the file, and were hence considered "used".  For
> > some reason, a subsequent attempt to allocate blocks for the
> > same file failed to use that file's preallocated blocks.
> 
> Nope.  ext2_truncate() calls ext2_discard_prealloc() to fix this up.
> Both 2.2 and 2.4 do this correctly.

But the problem goes away when you disable EXT2_PREALLOCATE.
I tested it.

  reply	other threads:[~2001-05-24 11:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-23  6:13 O_TRUNC problem on a full filesystem Manas Garg
2001-05-23  9:16 ` OT: " Helge Hafting
2001-05-23  9:55 ` Andrew Morton
2001-05-24 11:16   ` Stephen C. Tweedie
2001-05-24 11:28     ` Andrew Morton [this message]
2001-05-24 17:24       ` Andreas Dilger
2001-05-24 18:15         ` Stephen C. Tweedie
2001-05-24 20:26           ` Andreas Dilger
2001-05-25  0:24         ` Andrew Morton
2001-05-25  9:42           ` Stephen C. Tweedie

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=3B0CF068.A6ADA562@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mls@chakpak.net \
    --cc=sct@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.