From: Mike Fedyk <mfedyk@matchmail.com>
To: Oleg Drokin <green@namesys.com>
Cc: Kyle Rose <krose+linux-kernel@krose.org>, linux-kernel@vger.kernel.org
Subject: Re: Large-file corruption. ReiserFS? VFS?
Date: Fri, 12 Sep 2003 13:54:46 -0700 [thread overview]
Message-ID: <20030912205446.GD30584@matchmail.com> (raw)
In-Reply-To: <20030912184001.GA9245@namesys.com>
On Fri, Sep 12, 2003 at 10:40:01PM +0400, Oleg Drokin wrote:
> Hello!
>
> On Fri, Sep 12, 2003 at 10:59:17AM -0700, Mike Fedyk wrote:
> > > > However, just as the write completed, the beginning of the file became
> > > > corrupted. I considered a 4GB problem to be likely, and re-tested
> > > You are absolutely right.
> > > Ther is a reiserfs problem that I just found based on your description.
> > > The patch below should help. Please confirm that it works for you too.
> > > Thanks a lot for the report.
> > Yow, I guess large files on reiserfs in 2.6 isn't very common...
>
> Or may be nobody noticed the corruption.
Possible.
Does this affect 2.4 also? If not, then that will narrow the possible
number of people who could have hit this bug.
Luckily when I was using reiserfs, I used mostly small files.
next prev parent reply other threads:[~2003-09-12 20:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 20:28 Large-file corruption. ReiserFS? VFS? Kyle Rose
[not found] ` <20030911144732.S18851@schatzie.adilger.int>
2003-09-11 20:56 ` Kyle Rose
2003-09-11 21:00 ` Andreas Dilger
2003-09-13 6:50 ` Rogier Wolff
2003-09-13 6:51 ` Rogier Wolff
2003-09-12 9:36 ` Matthias Schniedermeyer
2003-09-12 11:47 ` Kyle Rose
2003-09-12 15:39 ` Oleg Drokin
2003-09-12 17:59 ` Mike Fedyk
2003-09-12 18:40 ` Oleg Drokin
2003-09-12 20:54 ` Mike Fedyk [this message]
2003-09-12 21:05 ` Kyle Rose
2003-09-12 21:56 ` Mike Fedyk
2003-09-13 0:46 ` Hans Reiser
2003-09-13 7:00 ` Oleg Drokin
2003-09-14 12:13 ` Kyle Rose
[not found] <uGoz.5NC.7@gated-at.bofh.it>
2003-09-11 20:49 ` Pascal Schmidt
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=20030912205446.GD30584@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=green@namesys.com \
--cc=krose+linux-kernel@krose.org \
--cc=linux-kernel@vger.kernel.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