kernel-testers.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heinz Diehl <htd-HjJ2MNWy62to6+H+lsi3Gti2O/JbrIOy@public.gmane.org>
To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Alexander Beregalov
	<a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Kernel Testers List
	<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	xfs-VZNHf3L845pBDgjK7y7TUQ@public.gmane.org
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-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.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

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:~ #

  parent reply	other threads:[~2009-05-02 10:14 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 [this message]
     [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
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=20090502101405.GA6145@fancy-poultry.org \
    --to=htd-hjj2mnwy62to6+h+lsi3gti2o/jbrioy@public.gmane.org \
    --cc=a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=xfs-VZNHf3L845pBDgjK7y7TUQ@public.gmane.org \
    /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).