From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from hancock.sc.steeleye.com (nat9.steeleye.com [65.114.3.137]) by dsl2.external.hp.com (Postfix) with ESMTP id 0C9C44841 for ; Sun, 9 Nov 2003 07:54:20 -0700 (MST) Received: from mulgrave-w.il.steeleye.com (il-ppp.sc.steeleye.com [172.17.6.240]) by hancock.sc.steeleye.com (8.11.6/linuxconf) with ESMTP id hA9Es6Y11089; Sun, 9 Nov 2003 09:54:06 -0500 Subject: Re: [parisc-linux] Allow palo partition to be mounted as ext2 From: James Bottomley To: "M. Grabert" Cc: Paul Bame , PARISC list In-Reply-To: References: <1068254037.2120.93.camel@mulgrave> Content-Type: text/plain Date: 09 Nov 2003 08:54:05 -0600 Message-Id: <1068389646.2086.5.camel@mulgrave> Mime-Version: 1.0 Sender: parisc-linux-admin@lists.parisc-linux.org Errors-To: parisc-linux-admin@lists.parisc-linux.org List-Help: List-Post: List-Subscribe: , List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: On Fri, 2003-11-07 at 22:12, M. Grabert wrote: > I don't know much ext2/3 details, but is there a way that a fsck > could mess things up? Eg. not an ordinary fsck, but if the user > runs it manually with special options? Not fsck, no. The bad blocks are treated as though they belonged to an invisible file. redoing the mke2fs, of course, would destroy the bootability. > I suppose the same technique could be also used for other filesystems > palo supports (in the future). As long as they have bad block support, yes---that's not a given; reiserfs doesn't seem to have it, for instance. Also, since the command has to be run by palo and palo has to know how to format the bad block list, it's not trivial to do. However, the ultimate argument is because palo's iplboot loader only knows about ext2/3, even if you could format the partition as anything else, you currently wouldn't be able to boot from it. James