From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vyacheslav Dubeyko Subject: Re: very large mount time after unxepected power down Date: Thu, 15 Nov 2012 10:32:52 +0400 Message-ID: <1352961172.2076.10.camel@slavad-ubuntu> References: <1351604965.2069.13.camel@slavad-ubuntu> <1351608774.2026.6.camel@slavad-ubuntu> <1351664002.2105.3.camel@slavad-ubuntu> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dubeyko.com; s=default; h=Mime-Version:Content-Transfer-Encoding:Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID; bh=69zYTeff0xvwxf8vnohtRbXJA/mYXEDVCNa/pSsaxC8=; b=FNdOzwwCd0R/w4fRvVIkq8qu3pS1icMePy/qOoj7wTsRURsJ3nxvBoC0fKfa00OwcnmMHQeduFwbkHQ1Up0FpzKhQKedIn/cvBPv7fNMeimXkB3uXdkuaBB/eR0R7Mm/; In-Reply-To: Sender: linux-nilfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="utf-8" To: =?UTF-8?Q?=D0=A1=D0=B5=D1=80=D0=B3=D0=B5=D0=B9_?= =?UTF-8?Q?=D0=90=D0=BB=D0=B5=D0=BA=D1=81=D0=B0=D0=BD=D0=B4=D1=80=D0=BE?= =?UTF-8?Q?=D0=B2?= Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Hi, On Thu, 2012-11-15 at 07:07 +0300, =D0=A1=D0=B5=D1=80=D0=B3=D0=B5=D0=B9= =D0=90=D0=BB=D0=B5=D0=BA=D1=81=D0=B0=D0=BD=D0=B4=D1=80=D0=BE=D0=B2 wro= te: > Hi, > The bug appeared again. And apparently it's a kernel one. > My bad that I didn't notice that the CPU activity wals in kernel spac= e. > The mount process hangs inside mount call itself. I've an strace > output, but it's not informative, it perfectly normal besides the han= g > in mount call. I will try to reproduce the issue. As I remember, you described your environment with details. But what size of files you have preferably on your partition? Moreover, could you share strace output anyway? Because it can be a basis for understanding of achieving the issue reproducing and analysis of execution environment. If you want to try to investigate and fix the issue by yourself then your strace output is needed also. By the way, could you share your dmesg output for analysis? I think also it can be very useful lscp and lssu output before sudden power off and after mount is ended successfully. Could you share it? With the best regards, Vyacheslav Dubeyko. > I've a very few experience in catching kernel bugs like that, but I'l= l > do my best to help. >=20 >=20 > According to my observations, the bug takes place only after emergenc= y > power down after a rather long uptime, may be even the time it takes > to mount the partition is proportional to ether uptime or the amount > of io since last mount. >=20 > I left FS unclean, so it is possible to do some tests, but I would > like to see it up and running as soon as possible. >=20 >=20 > Best regards, > Aleksandrov Sergey Vasil'evich -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" = in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html