From: Mike Fedyk <mfedyk@matchmail.com>
To: Rogier Wolff <R.E.Wolff@harddisk-recovery.nl>
Cc: Jeff Mahoney <jeffm@suse.com>, Hans Reiser <reiser@namesys.com>,
reiserfs-list@namesys.com, copy@harddisk-recovery.nl
Subject: Re: ReiserFS problems
Date: Wed, 6 Aug 2003 15:08:17 -0700 [thread overview]
Message-ID: <20030806220817.GG21290@matchmail.com> (raw)
In-Reply-To: <20030806213623.C3975@bitwizard.nl>
On Wed, Aug 06, 2003 at 09:36:23PM +0200, Rogier Wolff wrote:
> P.S. We also sometimes do:
>
> while (1)
> seek to random position (in randomly chosen 1G file)
> write 1k
>
> we might benefit from a call that tells the filesystem:
> Pretend that this file WILL grow to 1Gb, but leave it sparse for
> now.
>
> So, the block to allocate if we seek to 500Mb past the beginning of the
> file would be 500Mb further along the disk. That way the eventual image
> will be linear. But leaving the intermediate blocks unallocated will
> allow us to eventually use up that free space if we DO NOT end up
> writing that area.
Ahh, but sparse files are not handled effeciently at all with reiserfs. It
is fixed properly in reiser4 though. There was a thread recently on this
issue on the reiserfs list within the last week about this.
If you use reiserfs, avoid large sparse files like the plague.
next prev parent reply other threads:[~2003-08-06 22:08 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 16:20 ReiserFS problems Rogier Wolff
2003-08-06 16:43 ` Hans Reiser
2003-08-06 18:41 ` Jeff Mahoney
2003-08-06 19:21 ` Rogier Wolff
2003-08-06 19:36 ` Rogier Wolff
2003-08-06 22:08 ` Mike Fedyk [this message]
2003-08-07 4:40 ` Rogier Wolff
2003-08-06 19:40 ` Vitaly Fertman
2003-08-07 15:05 ` Hans Reiser
2003-08-07 15:53 ` Jeff Mahoney
2003-08-08 13:07 ` Hans Reiser
2003-08-06 20:48 ` Bernd Schubert
2003-08-06 16:48 ` Oleg Drokin
2003-08-06 17:18 ` Rogier Wolff
2003-08-06 17:28 ` Oleg Drokin
2003-08-06 17:49 ` Rogier Wolff
2003-08-06 18:10 ` Vitaly Fertman
2003-08-07 13:22 ` Hans Reiser
2003-08-07 18:12 ` Mike Fedyk
2003-08-08 0:18 ` Russell Coker
2003-08-08 11:29 ` [OT] " Christian Kujau
2003-08-08 12:40 ` Nikita Danilov
2003-08-08 13:06 ` Carl-Daniel Hailfinger
2003-08-08 12:59 ` Russell Coker
2003-08-08 15:39 ` Christian Kujau
2003-08-09 0:45 ` The Amazing Dragon
2003-08-08 9:56 ` Oleg Drokin
2003-08-06 17:43 ` Andreas Dilger
2003-08-06 17:52 ` Rogier Wolff
2003-08-07 13:27 ` Hans Reiser
2003-08-07 13:03 ` Hans Reiser
2003-08-07 13:41 ` Rogier Wolff
2003-08-07 18:44 ` Mike Fedyk
2003-08-06 17:22 ` Rogier Wolff
2003-08-06 18:01 ` Vitaly Fertman
2003-08-06 18:14 ` Rogier Wolff
2003-08-06 18:22 ` Rogier Wolff
2003-08-06 19:03 ` Oleg Drokin
2003-08-06 19:04 ` Vitaly Fertman
2003-08-07 13:35 ` Hans Reiser
2003-08-07 13:46 ` Rogier Wolff
2003-08-07 14:11 ` Vitaly Fertman
2003-08-06 18:52 ` Vitaly Fertman
2003-08-07 12:58 ` Hans Reiser
2003-08-07 13:24 ` Russell Coker
2003-08-07 14:41 ` Hans Reiser
2003-08-06 16:52 ` 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=20030806220817.GG21290@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=R.E.Wolff@harddisk-recovery.nl \
--cc=copy@harddisk-recovery.nl \
--cc=jeffm@suse.com \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.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.