From: Gary Hawco Subject: (unknown) Date: Mon, 16 Jun 2008 13:47:10 Message-ID: <3.0.6.32.20080616134710.01b18a90@pop.west.cox.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: "linux-ext4@vger.kernel.org" Return-path: Received: from fed1rmmtao106.cox.net ([68.230.241.40]:41867 "EHLO fed1rmmtao106.cox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753674AbYFPUrM (ORCPT ); Mon, 16 Jun 2008 16:47:12 -0400 Received: from fed1rmimpo03.cox.net ([70.169.32.75]) by fed1rmmtao106.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20080616204706.WWGN7004.fed1rmmtao106.cox.net@fed1rmimpo03.cox.net> for ; Mon, 16 Jun 2008 16:47:06 -0400 Subject: Sender: linux-ext4-owner@vger.kernel.org List-ID: Had a couple of questions as to what flex_bg & meta_bg features involve. I think flex_bg has to do with areas of metadata skipped during e2fsck, but I am not sure about meta_bg. And is meta_bg a mount option or a feature specified during mkfs.ext4dev? And if so, I guess you would use mkfs.ext4dev -t meta_bg? Any insight would be most appreciated. Gary Hawco