From owner-freebsd-current@FreeBSD.ORG  Thu Feb 28 10:31:36 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 925509C8;
 Thu, 28 Feb 2013 10:31:36 +0000 (UTC) (envelope-from lev@FreeBSD.org)
Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru
 [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 3782E1A07;
 Thu, 28 Feb 2013 10:31:36 +0000 (UTC)
Received: from lion.home.serebryakov.spb.ru (unknown
 [IPv6:2001:470:923f:1:9421:367:9d7d:512b])
 (Authenticated sender: lev@serebryakov.spb.ru)
 by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id AF6BF4AC57;
 Thu, 28 Feb 2013 14:31:34 +0400 (MSK)
Date: Thu, 28 Feb 2013 14:31:29 +0400
From: Lev Serebryakov <lev@FreeBSD.org>
Organization: FreeBSD
X-Priority: 3 (Normal)
Message-ID: <583012022.20130228143129@serebryakov.spb.ru>
To: Alexander Yerenkow <yerenkow@gmail.com>
Subject: Re: Unexpected SU+J inconsistency AGAIN -- please,
 don't shift topic to ZFS!
In-Reply-To: <CAPJF9w=CZg_+K7NHTGUhRLaMJWWNOG7zMipGMJL6w6NoNZpSXA@mail.gmail.com>
References: <1796551389.20130228120630@serebryakov.spb.ru>
 <1238720635.20130228123325@serebryakov.spb.ru>
 <1158712592.20130228141323@serebryakov.spb.ru>
 <CAPJF9w=CZg_+K7NHTGUhRLaMJWWNOG7zMipGMJL6w6NoNZpSXA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: lev@FreeBSD.org
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Feb 2013 10:31:36 -0000

Hello, Alexander.
You wrote 28 =C6=C5=D7=D2=C1=CC=D1 2013 =C7., 14:22:59:

AY> Could you afford reproducing this? :)
  After half a day of memtest86+ :)
  I want to be sure, that it is not memory problem first.

AY> Also, would be nice to know how look your setup (CPUs, how much disks, =
how
AY> they connected, is it hw raid, etc).
  Simple  E4500  CPU  on  Q35-based  desktop  (ASUS) MoBo, 6GiB memory
 (under  test  now!),  Samsung 500GiB SATA HDD for system, 5x2Tb  WD
 Green  (4xWD20EARS, 1xWD20EARX which replace failed WD20EARS), all
 disks are connected to 6 SATA ports of chipset (no RAID controller),
 WD disks are in software RAID5 with geom_raid5 (from ports, but I'm
 active maintainer of it).
   Disks are in "Default" configuration: WC and NCQ are enabled.

   I know, that FS guys could blame geom_raid5, as it could delay real
 write up to 15 seconds, but it never "lies" about writes (it doesn't
 mark BIOs complete till they are really sent to disk) and I could
 not reproduce any problems with it on many hours tests on VMs (and I
 don't want to experiment a lot on real hardware, as it contains my
 real data).

   Maybe, it is subtile interference between raid5 implementation and
  SU+J, but in such case I want to understand what does raid5 do
  wrong.

--=20
// Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>