kernel-testers.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ed Tomlinson <edt@aei.ca>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Alexander Beregalov <a.beregalov@gmail.com>,
	linux-kernel@vger.kernel.org, Heinz Diehl <htd@fancy-poultry.org>,
	Kernel Testers List <kernel-testers@vger.kernel.org>,
	xfs@oss.sgi.com
Subject: Re: 2.6.30-rc4: xfs_fsr hangs
Date: Sat, 2 May 2009 21:47:51 -0400	[thread overview]
Message-ID: <200905022147.52216.edt@aei.ca> (raw)
In-Reply-To: <49FCA988.2050600@sandeen.net>

On Saturday 02 May 2009 16:14:00 Eric Sandeen wrote:
> Alexander Beregalov wrote:
> > 2009/5/2 Eric Sandeen <sandeen@sandeen.net>:
> >> Alexander Beregalov wrote:
> >>> 2009/5/2 Heinz Diehl <htd@fancy-poultry.org>:
> >>>> On 01.05.2009, Alexander Beregalov wrote:
> >>>>
> >>>>> # xfs_db -r /dev/sdc1
> >>>>> xfs_db> frag
> >>>>> actual 23805, ideal 22890, fragmentation factor 3.84%
> >>>>> # xfs_fsr -v /dev/sdc1
> >>>>> /mnt/c start inode=0
> >>>>> ino=158
> >>>>> extents before:3 after:1 DONE ino=158
> >>>>>
> >>>>>  then it hangs
> >>>> I can't confirm this here on my systems:
> >>>>
> >>>> liesel:~ # uname -a
> >>>> Linux liesel 2.6.30-rc4 #1 SMP PREEMPT Sat May 2 11:49:13 CEST 2009 x86_64 x86_64 x86_64 GNU/Linux
> >>> I have this problem on two x86_32 hosts.
> >>> It runs for about a minute and then hangs.
> >> echo w > /proc/sysrq-trigger
> >> dmesg
> >>
> >> would show all the sleeping processes...
> > It is the same as I posted already:
> 
> hum, only 1 thread, interesting...
 
I have also had strange stalls with rc4 (but not with rc3).  In one case sysrq would just print the title of commands no
data would follow.  Do not know if this is related but it may be that this is not just an xfs issue.

Ed Tomlinson

  reply	other threads:[~2009-05-03  1:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-01 20:33 2.6.30-rc4: xfs_fsr hangs Alexander Beregalov
     [not found] ` <a4423d670905011333s664115bdh1d72392897567c1d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-02 10:14   ` Heinz Diehl
     [not found]     ` <20090502101405.GA6145-HjJ2MNWy62to6+H+lsi3Gti2O/JbrIOy@public.gmane.org>
2009-05-02 18:35       ` Alexander Beregalov
2009-05-02 18:56         ` Eric Sandeen
     [not found]           ` <49FC9762.6010109-+82itfer+wXR7s880joybQ@public.gmane.org>
2009-05-02 18:59             ` Alexander Beregalov
     [not found]               ` <a4423d670905021159k51e91b12h96189005980b5e73-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-02 20:14                 ` Eric Sandeen
2009-05-03  1:47                   ` Ed Tomlinson [this message]
2009-05-07 23:33   ` Eric Sandeen
     [not found]     ` <4A036FBC.9020201-+82itfer+wXR7s880joybQ@public.gmane.org>
2009-05-07 23:55       ` Eric Sandeen
     [not found]         ` <4A037503.1070904-+82itfer+wXR7s880joybQ@public.gmane.org>
2009-05-08  1:04           ` Felix Blyakher
     [not found]             ` <ABCCDF18-5100-4891-AF1C-BA9513C8A334-sJ/iWh9BUns@public.gmane.org>
2009-05-08  1:09               ` Eric Sandeen
     [not found]                 ` <4A038651.5010202-+82itfer+wXR7s880joybQ@public.gmane.org>
2009-05-08  1:17                   ` Felix Blyakher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200905022147.52216.edt@aei.ca \
    --to=edt@aei.ca \
    --cc=a.beregalov@gmail.com \
    --cc=htd@fancy-poultry.org \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).