From: Andreas Dilger <adilger@turbolabs.com>
To: Ville Herva <vherva@niksula.hut.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3 vs resizerfs vs xfs
Date: Wed, 7 Nov 2001 14:45:55 -0700 [thread overview]
Message-ID: <20011107144555.N5922@lynx.no> (raw)
In-Reply-To: <E161UYR-0004S5-00@the-village.bc.nu> <E161Vbf-0000m9-00@lilac.csi.cam.ac.uk> <20011107213837.F26218@niksula.cs.hut.fi> <E161ZYW-0006ky-00@mauve.csi.cam.ac.uk> <20011107141157.L5922@lynx.no> <20011107233731.N1504@niksula.cs.hut.fi>
In-Reply-To: <20011107233731.N1504@niksula.cs.hut.fi>; from vherva@niksula.hut.fi on Wed, Nov 07, 2001 at 11:37:31PM +0200
On Nov 07, 2001 23:37 +0200, Ville Herva wrote:
> On Wed, Nov 07, 2001 at 02:11:57PM -0700, [Andreas Dilger] said:
> > If you have an open but unlinked file, then ext3 will delete this file at
> > mount/fsck time (unlike reiserfs which leaves it around wasting space).
>
> Is this really still true for reiserfs? Is there a way to get rid of them?
> reiserfsck? I had this vague impression that this bug had been dealt with
It may be fixed by now, but it wasn't for a long time. I'm not sure what
reiserfs patches are in the stock kernel anymore.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2001-11-07 21:48 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-07 15:00 ext3 vs resiserfs " Roy Sigurd Karlsbakk
2001-11-07 15:23 ` Alan Cox
2001-11-07 15:28 ` Zvi Har'El
2001-11-07 20:19 ` Andreas Dilger
2001-11-07 21:11 ` Zvi Har'El
2001-11-07 21:25 ` Christian Bornträger
2001-11-07 21:45 ` Mike Fedyk
2001-11-07 21:42 ` Andreas Dilger
2001-11-07 22:11 ` arjan
2001-11-07 21:48 ` arjan
2001-11-08 7:08 ` Zvi Har'El
2001-11-08 11:06 ` Arjan van de Ven
2001-11-08 12:10 ` Zvi Har'El
2001-11-08 12:11 ` Arjan van de Ven
2001-11-08 11:35 ` ramfs leak Padraig Brady
2001-11-07 16:31 ` ext3 vs resiserfs vs xfs James A Sutherland
2001-11-07 19:38 ` Ville Herva
2001-11-07 20:44 ` James A Sutherland
2001-11-07 21:11 ` Andreas Dilger
2001-11-07 21:37 ` ext3 vs resizerfs " Ville Herva
2001-11-07 21:45 ` Andreas Dilger [this message]
2001-11-08 0:13 ` ext3 vs resiserfs " James A Sutherland
2001-11-07 19:50 ` Daniel Gryniewicz
2001-11-07 20:24 ` Robert Love
2001-11-07 20:35 ` Andrew Morton
2001-11-07 20:27 ` Anton Altaparmakov
2001-11-07 18:40 ` Anton Altaparmakov
2001-11-07 19:12 ` Alan Cox
2001-11-07 20:36 ` Anton Altaparmakov
2001-11-07 19:40 ` Anton Altaparmakov
2001-11-07 20:15 ` Andrew Morton
2001-11-07 21:33 ` Mike Fedyk
2001-11-07 22:00 ` Andrew Morton
2001-11-07 22:27 ` Mike Fedyk
2001-11-07 22:56 ` Andrew Morton
2001-11-07 23:18 ` Andreas Dilger
2001-11-07 22:52 ` Mike Fedyk
2001-11-07 22:59 ` Andrew Morton
2001-11-07 23:36 ` D. Stimits
2001-11-07 23:55 ` Mike Castle
2001-11-07 23:38 ` Mike Castle
2001-11-07 23:49 ` Mike Fedyk
2001-11-08 10:58 ` Juan Quintela
2001-11-07 20:25 ` Andreas Dilger
2001-11-07 23:33 ` Ryan Cumming
2001-11-09 16:11 ` Andreas Dilger
2001-11-07 20:21 ` Andreas Dilger
2001-11-07 20:05 ` Theodore Tso
2001-11-07 20:18 ` Andreas Dilger
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=20011107144555.N5922@lynx.no \
--to=adilger@turbolabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vherva@niksula.hut.fi \
/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®