Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262062AbTIMHAP (ORCPT ); Sat, 13 Sep 2003 03:00:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262064AbTIMHAP (ORCPT ); Sat, 13 Sep 2003 03:00:15 -0400 Received: from angband.namesys.com ([212.16.7.85]:40836 "EHLO angband.namesys.com") by vger.kernel.org with ESMTP id S262062AbTIMHAL (ORCPT ); Sat, 13 Sep 2003 03:00:11 -0400 Date: Sat, 13 Sep 2003 11:00:10 +0400 From: Oleg Drokin To: Kyle Rose , linux-kernel@vger.kernel.org Subject: Re: Large-file corruption. ReiserFS? VFS? Message-ID: <20030913070010.GA12918@namesys.com> References: <87r82noyr9.fsf@nausicaa.krose.org> <20030912153935.GA2693@namesys.com> <20030912175917.GB30584@matchmail.com> <20030912184001.GA9245@namesys.com> <20030912205446.GD30584@matchmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030912205446.GD30584@matchmail.com> User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 990 Lines: 24 Hello! On Fri, Sep 12, 2003 at 01:54:46PM -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. No, 2.4 is not affected. Bye, Oleg - 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/