[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200908182112.53486.rjw@sisk.pl>
Date: Tue, 18 Aug 2009 21:12:53 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Harald Dunkel <harald.dunkel@...nline.de>
Cc: Frédéric Weisbecker <fweisbec@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
Jeff Mahoney <jeffm@...e.com>, Tejun Heo <htejun@...il.com>
Subject: Re: [Bug #13374] reiserfs blocked for more than 120secs
On Tuesday 18 August 2009, Harald Dunkel wrote:
> Hi Rafael,
>
> I haven't seen the 120secs timeout yet, but using 2.6.31-rc5 there _are_
> some delays that I am not sure of. Sometimes it takes about 30 secs till
> the XWindow server comes up, for example. (I use xinit on the command line
> at login. / and /home are both reiserfs.) For 2.6.30.4 and older I haven't
> seen this delay yet, AFAIR.
>
> Most recent event: I tried to format a 4 GByte USB stick with reiserfs.
> Here is the screen output:
>
> # device=/dev/sdf
> # parted $device mklabel gpt
> Warning: The existing disk label on /dev/sdf will be destroyed and
> all data on this disk will be lost. Do you want to continue?
> Yes/No? Yes
> Information: You may need to update /etc/fstab.
>
> # parted -- $device mkpart primary 0s -1s
> Warning: You requested a partition from 0.00B to 4127MB.
> The closest location we can manage is 17.4kB to 4127MB.
> Is this still acceptable to you?
> Yes/No? Yes
> Information: You may need to update /etc/fstab.
>
> # mkreiserfs -l usbstick /dev/sdf1
> mkreiserfs 3.6.21 (2009 www.namesys.com)
> :
> :
> UUID: 154d66cc-02ac-4979-9a39-163e3cf80623
> LABEL: usbstick
> ATTENTION: YOU SHOULD REBOOT AFTER FDISK!
> ALL DATA WILL BE LOST ON '/dev/sdf1'!
> Continue (y/n):y
> Initializing journal - 0%....20%....40%....60%....80%....100%
> Syncing..ok
> ReiserFS is successfully created on /dev/sdf1.
>
> It took about 2 to 3 minutes till the "ok" in the "Syncing" line
> was shown. /var/log/messages was silent. When I tried to reproduce
> the delay it was gone, of course.
Thanks for the update.
> Since I would like to try 2.6.31-rc6 anyway, maybe you could post
> some hints about what debugging options to set in the config file?
Unfortunately, I don't have much experience with debugging issues of this kind.
Perhaps Tejun will have some hints (CC added)?
Best,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists