From: Chris Mason <mason@suse.com>
To: Rik van Riel <riel@conectiva.com.br>,
Andreas Dilger <adilger@turbolinux.com>
Cc: Shawn Veader <shawn.veader@zapmedia.com>, linux-kernel@vger.kernel.org
Subject: Re: disk full or not? you decide...
Date: Wed, 11 Jul 2001 18:37:45 -0400 [thread overview]
Message-ID: <264310000.994891065@tiny> (raw)
In-Reply-To: <Pine.LNX.4.33L.0107111909140.9899-100000@imladris.rielhome.conectiva>
On Wednesday, July 11, 2001 07:10:27 PM -0300 Rik van Riel
<riel@conectiva.com.br> wrote:
> On Wed, 11 Jul 2001, Andreas Dilger wrote:
>
>> Note also that on reiserfs, if you have such a process which keeps
>> files open after they are deleted and then you have a crash, the file
>> is "orphaned" and the space is "lost" until you run reiserfsck again.
>> It may be that Chris Mason's patch for this is in the latest kernels,
>> but it may not be, and it might not be in the kernel you are running.
>
> Chris, Hans, is this problem still in the reiserfs
> in the current kernel or has it already been fixed ?
Vladimir Saveliev has a patch that is doing well in internal testing. I
had wanted to intergrate it some nested transaction stuff, but it didn't
have the same advantages as it did under 2.2.x.
They will probably send it out for wider testing very soon.
Just to clarify, you need to have a crash or unclean un
-chris
next prev parent reply other threads:[~2001-07-11 22:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 19:30 disk full or not? you decide Shawn Veader
2001-07-11 19:54 ` Ragnar Kjørstad
2001-07-12 8:12 ` Hans Reiser
2001-07-11 20:16 ` Andreas Dilger
2001-07-11 22:10 ` Rik van Riel
2001-07-11 22:37 ` Chris Mason [this message]
2001-07-11 20:25 ` Aaron Smith
2001-07-11 21:34 ` Josh McKinney
2001-07-13 9:52 ` disk full or not? Disk space dissapear :-( Rafael Martinez
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=264310000.994891065@tiny \
--to=mason@suse.com \
--cc=adilger@turbolinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=shawn.veader@zapmedia.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.