From stijn@pcwin002.win.tue.nl Fri Nov 5 20:17:01 2004 Return-Path: Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E20EE16A4CE; Fri, 5 Nov 2004 20:17:01 +0000 (GMT) Received: from kweetal.tue.nl (kweetal.tue.nl [131.155.3.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72C4E43D49; Fri, 5 Nov 2004 20:17:01 +0000 (GMT) (envelope-from stijn@pcwin002.win.tue.nl) Received: by kweetal.tue.nl (Postfix, from userid 40) id AF4D813BB1F; Fri, 5 Nov 2004 21:17:00 +0100 (CET) Received: from pcwin002.win.tue.nl (pcwin002.win.tue.nl [131.155.71.72]) by kweetal.tue.nl (Postfix) with ESMTP id 9C0CC13BACB; Fri, 5 Nov 2004 21:16:59 +0100 (CET) Received: (from stijn@localhost) by pcwin002.win.tue.nl (8.13.1/8.13.1/Submit) id iA5EjV6Q001541; Fri, 5 Nov 2004 15:45:31 +0100 (CET) (envelope-from stijn) Message-Id: <200411051445.iA5EjV6Q001541@pcwin002.win.tue.nl> Date: Fri, 5 Nov 2004 15:45:31 +0100 (CET) From: Stijn Hoop Reply-To: Stijn Hoop To: FreeBSD-gnats-submit@freebsd.org Cc: Lukas Ertl Subject: data corruption on striped geom_vinum volume X-Send-Pr-Version: 3.113 X-GNATS-Notify: >Number: 73579 >Category: kern >Synopsis: data corruption on striped geom_vinum volume >Confidential: no >Severity: serious >Priority: low >Responsible: le >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Nov 05 20:20:41 GMT 2004 >Closed-Date: Mon Nov 08 14:31:10 GMT 2004 >Last-Modified: Mon Nov 08 14:31:10 GMT 2004 >Originator: Stijn Hoop >Release: FreeBSD 6.0-CURRENT i386 >Organization: >Environment: System: FreeBSD 6.0-CURRENT #0: Fri Nov 5 12:50:21 CET 2004 >Description: I'm seeing data corruption on a freshly created striped geom_vinum volume, with a fresh -CURRENT. Verification of the same file yields different checksums: [stijn@pcwin002] md5 testfile MD5 (testfile) = 1af4c4d4bd34128548f9052327bfc717 [stijn@pcwin002] md5 testfile MD5 (testfile) = 208118b38cd382c2273f00f26a1f3c73 >How-To-Repeat: - create a striped geom_vinum volume. The fresh test was done with this configuration file: %%% drive meg device ad4s1e drive herc device ad6s1e volume storage plex org striped 479k sd len * drive meg sd len * drive herc %%% but my initial volume that exhibited the problem had a stripe size of 279k. - newfs with default paramaters + softupdates - create a (large) testfile, I used sudo dd if=/dev/urandom of=testfile bs=1m count=1024 - create a checksum, twice, and witness the result above. Note how the checksums differ even though no process has since written to or modified the file. Drives are fine, checksumming data read from the raw device consistently gives the same result. >Fix: n/a >Release-Note: >Audit-Trail: Responsible-Changed-From-To: freebsd-bugs->le Responsible-Changed-By: simon Responsible-Changed-When: Fri Nov 5 23:40:06 GMT 2004 Responsible-Changed-Why: Over to gvinum author. http://www.freebsd.org/cgi/query-pr.cgi?pr=73579 State-Changed-From-To: open->closed State-Changed-By: le State-Changed-When: Mon Nov 8 14:30:43 GMT 2004 State-Changed-Why: After feedback from the submitter this seemed to be a hardware problem. http://www.freebsd.org/cgi/query-pr.cgi?pr=73579 >Unformatted: