xfs
[Top] [All Lists]

Re: 2.6.30-rc4: xfs_fsr hangs

To: Eric Sandeen <sandeen@xxxxxxxxxxx>
Subject: Re: 2.6.30-rc4: xfs_fsr hangs
From: Alexander Beregalov <a.beregalov@xxxxxxxxx>
Date: Tue, 5 May 2009 12:54:05 +0400
Cc: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=R3YB81S4KZpg9t/5dEfbm1HOS0DXbRwpz0r9yM6DiTY=; b=FRLbEMHo37Qom27O5VxexM9I1fiUHpoo+s59U4/iB0QRCma6OPp85H7YryK58qBTDd fFRpHVvkKqAq7Fjf76sqQBTrAbPhAFb9Vo5Dr7TbLAsBDrOLSTqB0e+/b8Iy9ULWdl8l uXQUSw4YY0yi+WJ/Qq8irCxXM10+3ou9eJEMQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=RnzGCRC5S48GfMtd7U/aRTdO7UjtIMiRDTZLnQUUlhypLYxh2mTbmPJgzyAkdWC/pm c6BsT1J0IjeNj7uv3Y8HylAyuQew6iwL16LGeJW+//DDWW2E79sctLnEVyXKwRf+4U/D Wm6cfJivVgYXmlfWd1mxZRc+asbskGpEYynPw=
In-reply-to: <a4423d670905031333o341981aal48168eeeb2870cdd@xxxxxxxxxxxxxx>
References: <a4423d670905011333s664115bdh1d72392897567c1d@xxxxxxxxxxxxxx> <20090502101405.GA6145@xxxxxxxxxxxxxxxxx> <a4423d670905021135s4fdbea82t20cf75b61c59dc75@xxxxxxxxxxxxxx> <49FC9762.6010109@xxxxxxxxxxx> <a4423d670905021159k51e91b12h96189005980b5e73@xxxxxxxxxxxxxx> <49FD2488.70503@xxxxxxxxxxx> <a4423d670905030015h59038741of55bae686ef923f0@xxxxxxxxxxxxxx> <49FDAA8E.80205@xxxxxxxxxxx> <a4423d670905031333o341981aal48168eeeb2870cdd@xxxxxxxxxxxxxx>
2009/5/4 Alexander Beregalov <a.beregalov@xxxxxxxxx>:
> 2009/5/3 Eric Sandeen <sandeen@xxxxxxxxxxx>:
>> Alexander Beregalov wrote:
>>> 2009/5/3 Eric Sandeen <sandeen@xxxxxxxxxxx>:
>> ...
>>
>>>> Does this happen if you try to defrag a single file?  i.e. something like:
>>> Yes, it does.
>>
>> Oh, interesting.  I didn't really expect that.  The testcase I provided
>> worked for me.  Maybe you can provide your kernel .config and I'll try
>> on a 32-bit box (I only tested 64-bit so far).
> Attached.

Cannot reproduce it on x86_64 as well.

<Prev in Thread] Current Thread [Next in Thread>