From: Hans Reiser <reiser@namesys.com>
To: George <george@xorgate.com>
Cc: linux-kernel@vger.kernel.org, Oleg Drokin <green@namesys.com>
Subject: Re: 2.6 kernel large file create problem
Date: Sun, 14 Sep 2003 08:03:36 +0400 [thread overview]
Message-ID: <3F63E898.4010803@namesys.com> (raw)
In-Reply-To: <000501c37a0c$e2ad24a0$3eac18ac@geosxp>
George wrote:
>I have a 300G reiserfs 3.6 file system created above a RAID0 (HPT372
>controller) partition. When I am using the 2.6.0-test5 kernel and create
>files larger that 4GB they are corrupted with lots of trash throughout the
>file. When I use the same file system with the 2.4.22 kernel it works fine.
>
>-
>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/
>
>
>
>
this bug was just found and fixed, green has details.
--
Hans
next prev parent reply other threads:[~2003-09-14 4:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 15:37 2.6 kernel large file create problem George
2003-09-14 4:03 ` Hans Reiser [this message]
2003-09-14 8:41 ` Oleg Drokin
2003-09-18 3:28 ` George
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=3F63E898.4010803@namesys.com \
--to=reiser@namesys.com \
--cc=george@xorgate.com \
--cc=green@namesys.com \
--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