From: Heinz Diehl <htd@fancy-poultry.org>
To: linux-kernel@vger.kernel.org
Cc: Alexander Beregalov <a.beregalov@gmail.com>,
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 12:14:05 +0200 [thread overview]
Message-ID: <20090502101405.GA6145@fancy-poultry.org> (raw)
In-Reply-To: <a4423d670905011333s664115bdh1d72392897567c1d@mail.gmail.com>
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
liesel:~ # xfs_db -r /dev/sdc1
xfs_db> frag
actual 42974, ideal 42842, fragmentation factor 0.31%
xfs_db> quit
liesel:~ # xfs_fsr -v /dev/sdc1
/home start inode=0
ino=248755507
ino=248755507 already fully defragmented.
ino=536871160
extents before:2 after:1 DONE ino=536871160
ino=536875693
extents before:3 after:1 DONE ino=536875693
ino=615920545
extents before:2 after:1 DONE ino=615920545
ino=615920557
extents before:2 after:1 DONE ino=615920557
ino=1092324584
extents before:4 after:1 DONE ino=1092324584
liesel:~ #
next prev parent reply other threads:[~2009-05-02 10:10 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
2009-05-02 10:14 ` Heinz Diehl [this message]
2009-05-02 18:35 ` Alexander Beregalov
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=20090502101405.GA6145@fancy-poultry.org \
--to=htd@fancy-poultry.org \
--cc=a.beregalov@gmail.com \
--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