Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751338AbVKXEwl (ORCPT ); Wed, 23 Nov 2005 23:52:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751341AbVKXEwl (ORCPT ); Wed, 23 Nov 2005 23:52:41 -0500 Received: from zproxy.gmail.com ([64.233.162.194]:50982 "EHLO zproxy.gmail.com") by vger.kernel.org with ESMTP id S1751338AbVKXEwl convert rfc822-to-8bit (ORCPT ); Wed, 23 Nov 2005 23:52:41 -0500 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=t09drxB6mvvE+0/5fP7RlzDjZ7wdkoWfKK30d3kRP6fdRjf1QdH1hPiDZtUCJoe20SDUGafE1ERcbIaFDfUPOt1ZxH5dtKoCeHRGy3aWcHZIDekl3eB6Rsv67VoQYW5MYqltSV0rMOZRMqPfydLBWRZHNiEO0W48x2HSi+g2gFE= Message-ID: Date: Wed, 23 Nov 2005 20:52:40 -0800 From: Bret Towe To: Andrew Morton Subject: Re: lvm/nfs crash Cc: linux-kernel@vger.kernel.org, dm-devel@redhat.com In-Reply-To: <20051123182443.67e971cc.akpm@osdl.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Content-Disposition: inline References: <20051123182443.67e971cc.akpm@osdl.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1400 Lines: 33 On 11/23/05, Andrew Morton wrote: > Bret Towe wrote: > > > > while doing a pvmove to get some data off of a drive that was starting to fail > > i did a refresh on a nfs mount from a client and the server > > doing this pvmove got the following crash in dmesg > > and it happened pvmove didnt make any progress any more > > after a reboot so i could try resuming pvmove it would crash on > > fsck of one of the lvm partitons i finally got it to boot correctly after > > running a livecd resuming the pvmove from there without even > > trying to fsck > > > > the kernel that did this orignally i had named 2.6.14-git11.5 > > which for me means i synced to the git tree before the -git12 snapshot > > had been made i also booted back to 2.6.13.3 to see if it worked > > but it gave similiar crash i forgot to take a picture of ether of those > > crashs at boot but solving this other crash would prob prevent > > the other from happening > > > > and no before you ask i do not intend to repeat it :) > > hopefully somethin can be made of this > > > > Are you using 4k stacks or 8k? CONFIG_4KSTACKS=y so says the .config - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/