I'm seeing what appears to be an infinite loop in xfssyncd. It is triggered when writing to a file system that is full or nearly full. I have pinpointed the change that introduced this problem: it's
Thanks for tracking that down - I've been trying to isolate a test case for another report of this looping in xfssyncd. [Luciano - this is the same problem we've been trying to track down.] Now we kn
I've had a quick look at the above commit. I'm not yet certain that everything is correct in terms of the semantics laid down in the change or that enough blocks are reserved for btree splits , but I
On Wed, 23 Aug 2006, David Chinner wrote: On Wed, Aug 23, 2006 at 02:02:18PM +1000, David Chinner wrote: On Tue, Aug 22, 2006 at 04:01:10PM -0400, Stephane Doyon wrote: I'm seeing what appears to be
..... That was going to be my next question. ;) At least that rules out a small error in the block reservation decision, so I'm going to have analyse all the code paths the mod introduced and work ou
You know, if you had of buumped it up just a bit higher, the problem might have gone away. With a fielsystem that only has 8 AGs in it, if you bumped it to 33, then problem would have disappeared....
Dave, The latest patch seems to work for me running bonnie++ on a small 2GB XFS filesystem. bonnie++ gets an ENOSPC on a write() and ends plus I don't see the softwatchdog timer dump the kernel stack
On Mon, 28 Aug 2006, Luciano Chavez wrote: On Mon, 2006-08-28 at 17:23 +1000, David Chinner wrote: On Thu, Aug 24, 2006 at 09:14:29AM +1000, David Chinner wrote: On Wed, Aug 23, 2006 at 11:00:43AM -0
I'm seeing what appears to be an infinite loop in xfssyncd. It is triggered when writing to a file system that is full or nearly full. I have pinpointed the change that introduced this problem: it's
Thanks for tracking that down - I've been trying to isolate a test case for another report of this looping in xfssyncd. [Luciano - this is the same problem we've been trying to track down.] Now we kn
I've had a quick look at the above commit. I'm not yet certain that everything is correct in terms of the semantics laid down in the change or that enough blocks are reserved for btree splits , but I
On Wed, 23 Aug 2006, David Chinner wrote: On Wed, Aug 23, 2006 at 02:02:18PM +1000, David Chinner wrote: On Tue, Aug 22, 2006 at 04:01:10PM -0400, Stephane Doyon wrote: I'm seeing what appears to be
..... That was going to be my next question. ;) At least that rules out a small error in the block reservation decision, so I'm going to have analyse all the code paths the mod introduced and work ou
You know, if you had of buumped it up just a bit higher, the problem might have gone away. With a fielsystem that only has 8 AGs in it, if you bumped it to 33, then problem would have disappeared....
Dave, The latest patch seems to work for me running bonnie++ on a small 2GB XFS filesystem. bonnie++ gets an ENOSPC on a write() and ends plus I don't see the softwatchdog timer dump the kernel stack
On Mon, 28 Aug 2006, Luciano Chavez wrote: On Mon, 2006-08-28 at 17:23 +1000, David Chinner wrote: On Thu, Aug 24, 2006 at 09:14:29AM +1000, David Chinner wrote: On Wed, Aug 23, 2006 at 11:00:43AM -0