From: Chris Mason <mason@suse.com>
To: Xuan Baldauf <xuan--reiserfs@baldauf.org>,
David Rees <dbr@spoke.nols.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"reiserfs-list@namesys.com" <reiserfs-list@namesys.com>
Subject: Re: [reiserfs-list] Re: Apparent instability of reiserfs on 2.4.1
Date: Wed, 07 Feb 2001 12:39:59 -0500 [thread overview]
Message-ID: <511820000.981567599@tiny> (raw)
In-Reply-To: <3A818619.7C3967BC@baldauf.org>
On Wednesday, February 07, 2001 06:30:01 PM +0100 Xuan Baldauf
<xuan--reiserfs@baldauf.org> wrote:
> In my case, it's a SIS5513 board.
>
> I have to note that I now have one case which is between offset 9260 and
> 11016. So probably the tails unpacking theory does not work out.
>
> After a more systematical search, I have found following offsets:
>
> 9260..11016 = 1756
> 4204.. 5964 = 1760
> 2160.. 3243 = 1083
> 2896.. 3534 = 638
> 1392.. 3704 = 2312
>
> and so on. Maybe I should write a program which automatically detects and
> reports the zero blocks. I think the theory of tails unpacking does not
> work out, because there are also areas affected which are not between 2048
> and 4096. Also the length of the zeroing can be greater than 2048.
> However, I did not encounter a length of over 4096.
>
Files up to around 16k in length can have tails, and tails can be larger
than 2048 bytes.
Also interesting would be info about when the file closes. reiserfs only
creates a tail on file close (file writes always go to full blocks). If
you application has the file mmap'd the rules change a little (does it?).
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-07 17:40 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 12:06 Apparent instability of reiserfs on 2.4.1 Hans Reiser
2001-02-07 15:47 ` Chris Mason
2001-02-07 16:38 ` [reiserfs-list] " David Rees
2001-02-07 16:48 ` Chris Mason
2001-02-08 6:34 ` Daniel Stone
2001-02-10 13:02 ` Chris Wedgwood
2001-02-10 13:05 ` Daniel Stone
2001-02-10 13:08 ` Chris Wedgwood
2001-02-11 7:00 ` Hans Reiser
2001-02-12 0:56 ` Chris Mason
2001-02-12 19:11 ` Marcelo Tosatti
2001-02-12 20:42 ` Hans Reiser
2001-02-12 19:33 ` Marcelo Tosatti
2001-02-12 21:01 ` Hans Reiser
2001-02-12 23:03 ` Chris Mason
2001-02-12 22:39 ` Hans Reiser
2001-02-13 0:18 ` Chris Mason
2001-02-12 22:44 ` Hans Reiser
2001-02-11 6:58 ` Hans Reiser
2001-02-10 14:47 ` Alan Cox
2001-02-10 21:16 ` David Ford
2001-02-11 0:36 ` Andrius Adomaitis
2001-02-11 8:29 ` Hans Reiser
[not found] ` <wvu261oa80.fsf@freeze.oslo.dnmi.no>
2001-02-11 8:59 ` Hans Reiser
2001-02-11 9:52 ` Adrian Phillips
2001-02-11 9:47 ` Hans Reiser
2001-02-11 17:10 ` Alan Cox
2001-02-11 19:56 ` Andi Kleen
2001-02-12 2:17 ` Rogerio Brito
2001-02-12 9:49 ` Andi Kleen
2001-02-12 13:39 ` Henning P. Schmiedehausen
2001-02-11 21:16 ` Hans Reiser
2001-02-12 9:36 ` Alan Cox
2001-02-11 10:53 ` Alan Cox
2001-02-11 8:50 ` Hans Reiser
[not found] ` <3A818619.7C3967BC@baldauf.org>
2001-02-07 17:39 ` Chris Mason [this message]
2001-02-07 17:53 ` Xuan Baldauf
2001-02-07 19:14 ` Xuan Baldauf
2001-02-07 21:47 ` Chris Wedgwood
2001-02-07 21:55 ` Chris Mason
2001-02-07 22:05 ` Xuan Baldauf
2001-02-07 22:13 ` Chris Mason
2001-02-07 18:41 ` Vedran Rodic
2001-02-07 18:45 ` Chris Mason
2001-02-07 19:15 ` Ivan Pulleyn
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=511820000.981567599@tiny \
--to=mason@suse.com \
--cc=dbr@spoke.nols.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
--cc=xuan--reiserfs@baldauf.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox