From: Alexander Beregalov <a.beregalov@gmail.com>
To: linux-kernel@vger.kernel.org, Heinz Diehl <htd@fancy-poultry.org>
Cc: 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 22:35:17 +0400 [thread overview]
Message-ID: <a4423d670905021135s4fdbea82t20cf75b61c59dc75@mail.gmail.com> (raw)
In-Reply-To: <20090502101405.GA6145@fancy-poultry.org>
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.
vmstat 1:
0 1 80 30856 12284 1289452 0 0 16384 16380 224 301 0 5 0 95
0 1 80 32020 12196 1287884 0 0 25984 16380 290 470 0 11 0 89
0 1 80 30732 12132 1289648 0 0 23168 32760 286 413 0 6 0 94
0 1 80 32220 12128 1287620 0 0 16384 16380 220 303 0 8 0 92
1 0 80 198312 12108 1137956 0 0 14472 14628 223 284 0 10 3 87
0 0 80 1118144 12108 218216 0 0 0 0 63 33 0 38 62 0
0 0 80 1118144 12108 218216 0 0 0 0 24 26 0 0 100 0
0 0 80 1118144 12108 218216 0 0 0 0 36 28 0 1 99 0
0 0 80 1118144 12108 218216 0 0 0 0 36 32 1 1 98 0
0 0 80 1118144 12108 218216 0 0 0 0 78 66 0 1 99 0
next prev parent reply other threads:[~2009-05-02 18:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 20:33 Alexander Beregalov
2009-05-02 10:14 ` Heinz Diehl
2009-05-02 18:35 ` Alexander Beregalov [this message]
2009-05-02 18:56 ` Eric Sandeen
2009-05-02 18:59 ` Alexander Beregalov
2009-05-02 20:14 ` Eric Sandeen
2009-05-03 1:47 ` Ed Tomlinson
2009-05-07 23:33 ` Eric Sandeen
2009-05-07 23:55 ` Eric Sandeen
2009-05-08 1:04 ` Felix Blyakher
2009-05-08 1:09 ` Eric Sandeen
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=a4423d670905021135s4fdbea82t20cf75b61c59dc75@mail.gmail.com \
--to=a.beregalov@gmail.com \
--cc=htd@fancy-poultry.org \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®