|Subject:||Re: Oops at xfs_bmbt_get_startoff in SLES 10 2.6.16|
|From:||Kevin Jamieson <kevin@xxxxxxxxxxxxxxxxx>|
|Date:||Wed, 22 Apr 2009 23:24:29 -0700|
|References:||<643184.108.40.206.145.1236883814.squirrel@xxxxxxxxxxxxxxxxxxxxxxxxxx> <49B9611F.5040009@xxxxxxxxxxx> <58707.24.80.224.145.1236899620.squirrel@xxxxxxxxxxxxxxxxxxxxxxxxxx> <536220.127.116.11.145.1240361692.squirrel@xxxxxxxxxxxxxxxxxxxxxxxxxx> <49EE7E17.8050006@xxxxxxxxxxx> <B32B0133-B835-4D31-B52A-364F607B9866@xxxxxxx>|
|User-agent:||Thunderbird 18.104.22.168 (Macintosh/20080421)|
Felix Blyakher wrote:
But I could never reproduce the problem, even with Lachlan's test program.
I was not able to reproduce the problem with Lachlan's test program either (although I did not experiment much with the parameters).
Kevin, any idea what kind of io load triggered this problem?
The workload consisted of predominantly (98%) 2-3MB file ingests through an NFS share, with a a few (2%) 1GB file ingests, where the issue seemed to trigger on the larger files.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: Oops at xfs_bmbt_get_startoff in SLES 10 2.6.16, Kevin Jamieson|
|Next by Date:||Re: fsck.xfs proposed improvements, Mike Ashton|
|Previous by Thread:||Re: Oops at xfs_bmbt_get_startoff in SLES 10 2.6.16, Eric Sandeen|
|Next by Thread:||Re: Oops at xfs_bmbt_get_startoff in SLES 10 2.6.16, Kevin Jamieson|
|Indexes:||[Date] [Thread] [Top] [All Lists]|