public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Eugene Crosser <crosser@average.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.5 data corruption
Date: Fri, 15 Jun 2001 13:17:42 -0700	[thread overview]
Message-ID: <20010615131742.C27548@work.bitmover.com> (raw)
In-Reply-To: <E15Afvk-0005aV-00@the-village.bc.nu> <9gdp5c$pj$1@pccross.average.org>
In-Reply-To: <9gdp5c$pj$1@pccross.average.org>; from crosser@average.org on Fri, Jun 15, 2001 at 11:54:20PM +0400

On Fri, Jun 15, 2001 at 11:54:20PM +0400, Eugene Crosser wrote:
> In article <E15Afvk-0005aV-00@the-village.bc.nu>,
>         Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> >> any problems since 2.4.5 was published, they seem to have surfaced
> >> immediately after I created a rather big file capturing video with
> >> broadcast2000 (video card is bt848).  Filesystem is ext2.
> > 
> > Thats something I've seen reported elsehwere. The high bandwidth capture card
> > stuff seems to show up problems. It could be drivers could be hardware. On
> > my AMD 751 pre release board I see that problem but on the 751 production board
> > I dont
> 
> You must be right, today I created another big file with the same program
> but without doing caputre and the filesystem was intact.  OTOH,
> Russell Leighton reports curruption when creating a file with dd...

For what it is worth, after having three failures in a row, now it isn't
happening.  My test case is/was my nightly backup.  If it happens again,
I'll save the corrupted data so we can do more digging.  I'm kicking 
myself for not having done it the first time around.
-- 
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm 

  reply	other threads:[~2001-06-15 20:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-12 20:17 2.4.5 data corruption Larry McVoy
2001-06-13 15:09 ` Nathan Straz
2001-06-13 23:39 ` Chris Mason
2001-06-14 18:20 ` Alan Cox
2001-06-14 22:27   ` Eugene Crosser
2001-06-14 22:49     ` Alan Cox
2001-06-15 19:54       ` Eugene Crosser
2001-06-15 20:17         ` Larry McVoy [this message]
2001-06-15 12:02     ` Russell Leighton
2001-06-19  3:00   ` Stefan Traby
2001-06-19  7:49     ` Alan Cox
2001-06-19  9:13   ` Pedro M. Rodrigues
     [not found] <53B208BD9A7FD311881A009027B6BBFB9EACFE@siamese>
2001-06-19 19:01 ` Alan Cox
2001-06-19 20:06   ` Stefan Traby

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=20010615131742.C27548@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=crosser@average.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