From: Hans Reiser <reiser@namesys.com>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: Kyle Rose <krose+linux-kernel@krose.org>,
Oleg Drokin <green@namesys.com>,
linux-kernel@vger.kernel.org
Subject: Re: Large-file corruption. ReiserFS? VFS?
Date: Sat, 13 Sep 2003 04:46:53 +0400 [thread overview]
Message-ID: <3F6268FD.6070104@namesys.com> (raw)
In-Reply-To: <20030912215631.GH30584@matchmail.com>
Mike Fedyk wrote:
>On Fri, Sep 12, 2003 at 05:05:24PM -0400, Kyle Rose wrote:
>
>
>>>Does this affect 2.4 also?
>>>
>>>
>>As I said, this did not affect 2.4, at least not uniformly: I
>>regularly created DVD ISO images larger than 4GB under 2.4.2{0,1,2}
>>without problems.
>>
>>
>
>Ok, thanks. I'm glad it wasn't in 2.4
>
>EOST
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
>
It was a bug in Oleg's large write patch, which it seems was truly for
2.5 only.....
--
Hans
next prev parent reply other threads:[~2003-09-13 0:46 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
2003-09-12 21:05 ` Kyle Rose
2003-09-12 21:56 ` Mike Fedyk
2003-09-13 0:46 ` Hans Reiser [this message]
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=3F6268FD.6070104@namesys.com \
--to=reiser@namesys.com \
--cc=green@namesys.com \
--cc=krose+linux-kernel@krose.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.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.