linux-kernel - Re: XFS internal error (memory corruption)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20110706080505.GA2354@infradead.org>
Date:	Wed, 6 Jul 2011 04:05:05 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Dave Chinner <david@...morbit.com>
Cc:	Christoph Hellwig <hch@...radead.org>,
	T?r?k Edwin <edwintorok@...il.com>, xfs-masters@....sgi.com,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	xfs@....sgi.com
Subject: Re: XFS internal error (memory corruption)

On Wed, Jul 06, 2011 at 05:22:21PM +1000, Dave Chinner wrote:
> Unless you have a good sized chunk of BBWC in front of your disks,
> in which case internal logs are just as fast. In fact, internal logs
> can are often faster in this case because an internal log on a 12
> disk RAID6 array can sink a whole log more bandwidth than an external
> log on a 2-disk RAID0 mirror.....
> 
> At least, that's what my hardware tells me. ;)

Sure, a nice BBWC setup will give you good results.  But it's generally
much more expensive than a simple setup with a raid5 or 6 and a mirror for
the log device.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/