linux-kernel - RE: Btrfs: broken file system design (was Unbound(?) internal fragmentation in Btrfs)

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 23 Jun 2010 20:43:01 -0700
From:	"Daniel Taylor" <Daniel.Taylor@....com>
To:	unlisted-recipients:; (no To-header on input)
Cc:	"Daniel J Blueman" <daniel.blueman@...il.com>,
	"Mat" <jackdachef@...il.com>,
	"LKML" <linux-kernel@...r.kernel.org>,
	<linux-fsdevel@...r.kernel.org>,
	"Chris Mason" <chris.mason@...cle.com>,
	"Ric Wheeler" <rwheeler@...hat.com>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"The development of BTRFS" <linux-btrfs@...r.kernel.org>
Subject: RE: Btrfs: broken file system design (was Unbound(?) internal 	fragmentation in Btrfs)

Just an FYI reminder.  The original test (2K files) is utterly
pathological for disk drives with 4K physical sectors, such as
those now shipping from WD, Seagate, and others.  Some of the
SSDs have larger (16K0 or smaller blocks (2K).  There is also
the issue of btrfs over RAID (which I know is not entirely
sensible, but which will happen).

The absolute minimum allocation size for data should be the same
as, and aligned with, the underlying disk block size.  If that
results in underutilization, I think that's a good thing for
performance, compared to read-modify-write cycles to update
partial disk blocks. 

--
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/