From: Ryusuke Konishi Subject: Re: nilfs2 fails to mount after io/error Date: Tue, 02 Dec 2008 01:50:29 +0900 (JST) Message-ID: <20081202.015029.88482681.ryusuke@osrg.net> References: <20081126182158.20FD28306@blinkenlights.ch> <20081128.164300.47236105.ryusuke@osrg.net> <20081128153732.be4f5cf8.adrian@blinkenlights.ch> Reply-To: NILFS Users mailing list Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20081128153732.be4f5cf8.adrian-4ZM2p5qjiQGewZBzVTKGGg@public.gmane.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: users-bounces-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org Errors-To: users-bounces-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org To: adrian-4ZM2p5qjiQGewZBzVTKGGg@public.gmane.org Cc: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org Hi, On Fri, 28 Nov 2008 15:37:32 +0100, Adrian Ulrich wrote: > Hi, > > > In the meantime, please try the contained patch as follows: > > mount.nilfs2 now 'hangs' while mounting the filesystem: > > - CPU-Usage ~ 10% > - 100% io-wait > > > Do you think that mount.nilfs2 will ever finish? (It's running since ~15 minutes) Oh, that seems unusual. Please stop applying the patch. The check of sequence number might be really correct. In that case, recovery logic is suspicious. Or there was actually a critical violation of write order on the device. For nilfs2, if a superblock was written ahead of the segment pointed by the superblock, this can happen. Anyhow, I'll review the source code some more. With regards, Ryusuke Konishi