From: Chris Wedgwood <cw@f00f.org>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: Anton Ertl <anton@mips.complang.tuwien.ac.at>,
linux-kernel@vger.kernel.org, Jan Knutar <jk-lkml@sci.fi>,
L A Walsh <lkml@tlinx.org>
Subject: Re: XFS: how to NOT null files on fsck?
Date: Tue, 13 Jul 2004 15:39:23 -0700 [thread overview]
Message-ID: <20040713223923.GC7980@taniwha.stupidest.org> (raw)
In-Reply-To: <20040713222411.GA1035@hh.idb.hist.no>
On Wed, Jul 14, 2004 at 12:24:11AM +0200, Helge Hafting wrote:
> There is another solution - zero blocks when freeing them.
slow
> (Or put them on a list for later zeroing when the fs isn't busy, in
> order to kee??????p good performance)
complicated, doesn't buy as anything, it also means the blocks are
tied up whilst they are being zeroed (consider a truncated on a
multi-gb file, fairly common)
> With this approach you don't need to zero a half-written
> block after a crash, which means you destroy less data.
it doesn't zero after a crash, what happens is the blocks never make
it to disk and the metadata (which did make it to disk) reflects this
so read returns nulls
as is, you can truncate a multi-gb file, write over it and the only IO
you see will be the new data being written out, zeroing in between
would be horribly pianful
--cw
next prev parent reply other threads:[~2004-07-13 22:54 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 5:47 XFS: how to NOT null files on fsck? Norberto Bensa
2004-07-09 16:37 ` L A Walsh
2004-07-09 21:59 ` Chris Wedgwood
2004-07-10 18:33 ` L A Walsh
2004-07-10 18:43 ` Chris Wedgwood
2004-07-10 21:24 ` Bernd Eckenfels
2004-07-11 21:54 ` Helge Hafting
2004-07-12 17:56 ` H. Peter Anvin
2004-07-12 19:59 ` Chris Wedgwood
2004-07-12 20:32 ` H. Peter Anvin
2004-07-12 22:29 ` Bernd Eckenfels
2004-07-12 23:03 ` Bernd Eckenfels
2004-07-12 23:14 ` Chris Wedgwood
2004-07-10 18:43 ` Jan Knutar
2004-07-10 18:46 ` Chris Wedgwood
2004-07-10 18:55 ` Norberto Bensa
2004-07-10 19:19 ` Chris Wedgwood
2004-07-12 21:20 ` Chris Wedgwood
2004-07-12 22:40 ` L A Walsh
2004-07-12 22:53 ` Chris Wedgwood
2004-07-13 1:44 ` Bernd Eckenfels
2004-07-13 5:24 ` Chris Wedgwood
[not found] ` <2hgxc-5x9-9@gated-at.bofh.it>
2004-07-13 7:25 ` Anton Ertl
2004-07-13 8:09 ` Chris Wedgwood
2004-07-13 9:34 ` Anton Ertl
2004-07-13 9:53 ` Chris Wedgwood
2004-07-13 10:27 ` Tim Connors
2004-07-13 10:38 ` ismail dönmez
2004-07-13 11:16 ` Nick Piggin
2004-07-13 12:52 ` ismail dönmez
2004-07-13 10:58 ` Chris Wedgwood
2004-07-13 13:33 ` Anton Ertl
2004-07-13 20:32 ` Chris Wedgwood
2004-07-13 22:42 ` Bernd Eckenfels
2004-07-14 18:49 ` Anton Ertl
2004-07-14 19:00 ` Chris Wedgwood
2004-07-13 22:24 ` Helge Hafting
2004-07-13 22:39 ` Chris Wedgwood [this message]
2004-07-13 23:23 ` Bernd Eckenfels
2004-07-14 18:53 ` Anton Ertl
2004-07-10 19:33 ` Andreas Schwab
2004-07-10 19:40 ` Chris Wedgwood
2004-07-10 19:46 ` Norberto Bensa
2004-07-10 20:03 ` Chris Wedgwood
2004-07-11 1:21 ` Gopikrishnan Sidhardhan
2004-07-29 1:30 ` Nathan Scott
2004-08-03 18:31 ` L A Walsh
2004-08-04 0:48 ` Andi Kleen
2004-08-04 6:37 ` L A Walsh
2004-08-05 8:16 ` Helge Hafting
2004-08-06 1:10 ` Nathan Scott
2004-08-06 1:34 ` Andrew Morton
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=20040713223923.GC7980@taniwha.stupidest.org \
--to=cw@f00f.org \
--cc=anton@mips.complang.tuwien.ac.at \
--cc=helgehaf@aitel.hist.no \
--cc=jk-lkml@sci.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@tlinx.org \
/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.