Message-ID: <403A790F.7060100@odin.fintec.co.cr>
Date: Mon, 23 Feb 2004 16:05:03 -0600
From: Ivan Kocher <ikocher@odin.fintec.co.cr>
Organization: Fintec SA
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030313
MIME-Version: 1.0
To: linux-xfs@oss.sgi.com
Subject: Re: Problem with XFS and JFS
References: <403A3366.3070809@odin.fintec.co.cr> <1077557148.4497.1.camel@naboo.americas.sgi.com>
In-Reply-To: <1077557148.4497.1.camel@naboo.americas.sgi.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-xfs-bounce@oss.sgi.com
Errors-to: linux-xfs-bounce@oss.sgi.com
Precedence: bulk

Yes, I take care of /etc/fstab also.

Note that I started the machine with init=/bin/bash rw, so there is no 
/etc/fstab processing.  But anyway, /etc/fstab was ok, with / declared 
as type jfs.


Ivan
--------

Russell Cattelan wrote:

>>>Hi,
>>>
>>>Yesterday I was hit by a nasty bug ...
>>>
>>>I tried to change the filesystem of a couple machines from XFS to JFS, 
>>>so compiled kernel 2.4.23 with XFS (patch) and JFS.  Once the jfs root 
>>>partition was up, it booted, and xfs "tried" to repair the partition.  I 
>>> booted using my default setup and later after remaking all again using 
>>>init=/bin/bash rw, and even later init=/bin/bash ro
>>>
>>>In the first two cases cases, xfs tried its "repair", teling that it 
>>>recovered the journal... :( trashing the fs.
>>>
>>>When I booted in the third case, (ro) no problem...
>>>
>>>I wonder ... does xfs has some check for some magic in there?  I tried 
>>>in all machines, and in all it damaged the mounted / jfs fs ...
>>>      
>>>
>>sounds like mkfs.jfs is not zeroing enough of the device prior to
>>writing its fs.  particularly block zero where the XFS superblock
>>lives. (some mkfs avoid zeroing this due to quirky partitioning setups
>>on some architectures, notably Suns).
>>    
>>
>
>Or make sure to change the fstab so that the system does not try to
>mount a jfs partition as xfs.
>
>
>  
>