From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1KD2y0-0005m1-5F for mharc-grub-devel@gnu.org; Sun, 29 Jun 2008 15:53:44 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KD2xy-0005kC-8M for grub-devel@gnu.org; Sun, 29 Jun 2008 15:53:42 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KD2xw-0005iR-Ff for grub-devel@gnu.org; Sun, 29 Jun 2008 15:53:41 -0400 Received: from [199.232.76.173] (port=48778 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KD2xw-0005iF-Br for grub-devel@gnu.org; Sun, 29 Jun 2008 15:53:40 -0400 Received: from nf-out-0910.google.com ([64.233.182.190]:42376) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KD2xw-0003a6-0Y for grub-devel@gnu.org; Sun, 29 Jun 2008 15:53:40 -0400 Received: by nf-out-0910.google.com with SMTP id c7so332615nfi.26 for ; Sun, 29 Jun 2008 12:53:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:in-reply-to :references:content-type:date:message-id:mime-version:x-mailer; bh=iiK4JbO6uXwCS19v/f0kDkd2RY1gPNoLdWZ7Ap23VOE=; b=hnI5vtpIgX7dOPDvQSIjNy3IZmkUMSjUUzxFaW7HVrJWV0jiksrPb1CptkMAnZ8mVG LlIvderbX5W22YyqRWkyLzNITBN7b7srqtgVawepM/fNllwap26+Lf+eUVYQCKC9p+AN kXmsIaOKXQ+BGgMch8P3RJkl5qyShQGlh87Tw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:in-reply-to:references:content-type:date:message-id :mime-version:x-mailer; b=yFPsAcptg/3ZPGoUqZ/iyQaHooKbQk2K6Wny2W3w5ZCUEaMghrdC7DYsPI/emb7//k vz7qiQxax7COTQMVhXgSmoK9aNFNz0miZveyEYJ+k0o/9Sw3JTuCu2xjALcnogyA6K+C +zjYZnIY927rBmpZVOVTrbUIRHJRnWTWdGPPY= Received: by 10.210.123.20 with SMTP id v20mr683620ebc.18.1214769219008; Sun, 29 Jun 2008 12:53:39 -0700 (PDT) Received: from ?192.168.1.100? ( [213.37.137.93]) by mx.google.com with ESMTPS id z40sm5397843ikz.7.2008.06.29.12.53.37 (version=SSLv3 cipher=RC4-MD5); Sun, 29 Jun 2008 12:53:38 -0700 (PDT) From: Javier =?ISO-8859-1?Q?Mart=EDn?= To: The development of GRUB 2 In-Reply-To: References: <889404A5CBB14C15B464EDBB1AE338A8@fz> <1214765178.6942.2.camel@localhost> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-AX+GBTUepvC0A4I1v7Qt" Date: Sun, 29 Jun 2008 21:53:50 +0200 Message-Id: <1214769230.6942.11.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) Subject: Re: grub-probe detects ext4 wronly as ext2 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 19:53:42 -0000 --=-AX+GBTUepvC0A4I1v7Qt Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable El lun, 30-06-2008 a las 03:17 +0800, Bean escribi=C3=B3: > Hi, >=20 > I think it's not difficult to add extents support for grub2. Is the > feature stable now, how many distro enable it by default ? >=20 Ext4 is as of today in development and unstable; in fact, the FS name in Linux is "ext4dev", but I _think_ the on-disk format is already frozen and thus a readonly driver can be written. I'm not saying that we should delay the implementation of such a driver, just the we first need to address the potentially fatal problem of an ext4 FS mounted as ext3/2. No distro enables ext4 by default. In the case of the 2->3 transition the only thing a readonly ext2 driver missed from the ext3 FS was the journal and the dirindex htrees, which speed up directory indexing. This did not prevent data being read from the FS (though in the case of a crash incorrect metadata could be read), but in the case of ext4, the larger inodes and extent features _do_ prevent reads with an unprepared ext2 driver. The presence of these incompatible changes is signaled with set bits in the ext2 superblock "features" area (and are listed by tune2fs). Thus, what I propose is a quick fix first, adding a small patch to the ext2/3 driver that would detect such incompatible features and reject mounting the FS (and might be even overridable with an option at module initialization, like "-force4"). Then we'd be free to implement ext4 without people reporting strange failures as "the kernel is loaded, but initrd is not" or such. --=-AX+GBTUepvC0A4I1v7Qt Content-Type: application/pgp-signature; name=signature.asc Content-Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada digitalmente -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQIVAwUASGfoTqSl+Fbdeo72AQL/Ig//Wl+H+shmP8J9Q7u79QQuGYnJInUlIT+J b36fgkt9t76TEgou+S3xH1ChEuOivXFfUTCyDs/c3S9lioGHdLdklErW/JX3gokH fJs6Fr3YwOlpcvgDy6UsztdzgnML+UQiVtYTy4HXBKku3ETOmFcPWsC1KYvw8Tno DlVCZixFf7y/F3dZoq7sHIqBYyWq4b5xwz0rlAo78RGX2afxjjrlSNj+FuR0AQzM CYcKJiERS5ADikuh7wTikbkB8lPyXtOChq5DaZ0gdwIsrUNxLW/3UQlG5nREmrq/ oeVQBZ9Jz4LcMz8jY6tPJj5n1oashMUM9WoYotYrVb/0Iuh/h4fWwf22yWj0qLcr Sqy9qPrRoI/R0bUrumz4tdKKfvhcqP0Lte83bxuT3DDu9Sn7KZFjGWe6DPLzqg+H XmgN/yb+pcZoBt/2ITXlaJkBMGjWC2Af6mCxHOaBlYx9M0tHPa4fIvSvIgZhOIK2 P0Sjx7qOuRFP+QRt9u/tE3tlccgIAxr1UoOCFJj6zYkPbeTmFSpn6a2z987vpDBK 0IEtvrtnSpqNQff0EumTOFLehGJf8alVbt4X0gKqshv2wNhzABEPUZAHGyvkhn7u 87SWxhu58lXfuz+cWNP5RSZrLHP0G61COo8oQ0ZDdzwYKEc7ODZBRk3B/AykmWwa UnlzrTmrn7o= =EFXj -----END PGP SIGNATURE----- --=-AX+GBTUepvC0A4I1v7Qt--