From mboxrd@z Thu Jan 1 00:00:00 1970 From: srimugunthan dhandapani Subject: Re: logfs unmount bug Date: Fri, 12 Aug 2011 22:56:02 +0530 Message-ID: References: <20110805160325.GM26160@logfs.org> <20110808083107.GN26160@logfs.org> <20110809145812.GR26160@logfs.org> <20110812093429.GS26160@logfs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE To: =?ISO-8859-1?Q?J=F6rn_Engel?= , linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org Return-path: Received: from mail-wy0-f174.google.com ([74.125.82.174]:37482 "EHLO mail-wy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752633Ab1HLR0E convert rfc822-to-8bit (ORCPT ); Fri, 12 Aug 2011 13:26:04 -0400 Received: by wyg24 with SMTP id 24so2296665wyg.19 for ; Fri, 12 Aug 2011 10:26:03 -0700 (PDT) In-Reply-To: <20110812093429.GS26160@logfs.org> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hi, > I wouldn't suspect any code changes to cause the different behaviour. > Kernel config and test machine (memsize, etc.) would be more likely > candidates. =A0So if you could try the patch and send me the output, > that would be useful. I tried your patches and I also tried on official kernel release 3.0.1. I have shared the bonnie output and logs in the below link: https://docs.google.com/leaf?id=3D0BycgLWCW61phNjY0ZDg4ZjUtYzAyMy00YTgw= LWFlMmItNjlmZWIzMWFlNGUy&hl=3Den_US Basically the bonnie test gets stuck , when it does "Create files in sequential order...". I did all my tests with nandsim. Are there any problems using logfs with nandsim? I hit on another bug(segment.c:782) by running the following script. - #!/bin/bash for i in $(seq 1 10) do sudo mount -t logfs /dev/mtdblock0 /mnt/flash_drive/ ; cd /mnt/flash_drive/ ; sudo mkdir dir$i ; cd ; sudo umount /mnt/flash_drive/ ; done - I did a partial analysis. It happens when we do the remount and it follows the code path "Possibly incomplete write" in check_area() function.(the area is open and memchr_inv returns non-null pointer). It tries to do "logfs_rewrite_block", but since the free list is not filled during this time, it says "LOGFS: ran out of free segments" bug. Hope you are able to reproduce this problem. thanks, mugunthan -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html