Date: Thu, 28 Feb 2013 19:00:49 +0400 From: Lev Serebryakov <lev@FreeBSD.org> To: Ivan Voras <ivoras@freebsd.org> Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: Unexpected SU+J inconsistency AGAIN -- please, don't shift topic to ZFS! Message-ID: <1843530475.20130228190049@serebryakov.spb.ru> In-Reply-To: <1502041051.20130228185647@serebryakov.spb.ru> References: <1796551389.20130228120630@serebryakov.spb.ru> <1238720635.20130228123325@serebryakov.spb.ru> <1158712592.20130228141323@serebryakov.spb.ru> <CAPJF9w=CZg_%2BK7NHTGUhRLaMJWWNOG7zMipGMJL6w6NoNZpSXA@mail.gmail.com> <583012022.20130228143129@serebryakov.spb.ru> <kgnp1n$9mc$1@ger.gmane.org> <1502041051.20130228185647@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Ivan. You wrote 28 =D1=84=D0=B5=D0=B2=D1=80=D0=B0=D0=BB=D1=8F 2013 =D0=B3., 18:56= :47: LS> There was commit r246876, but I don't understand exactly what it LS> means, as no real FS or driver's code was touched. And, yes, barriers are much stronger than "sync writes", as they should flush all previous writes, even that is not related to journal or metadata and could wait more (simple file data could be fixed on plates out of order without destroying filesystem structure). --=20 // Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1843530475.20130228190049>