>
>
>>>> Nathan Scott <nathans@xxxxxxx> 08/08/2003 4:34:15 PM >>>
>On Fri, Aug 08, 2003 at 04:12:22PM +1000, Scott Fagg wrote:
>> >
>> >For some strange reason we are trying to read at AG blk 0 for that
>> >inode, which is wrong - block zero in an AG holds the SB/AGF/AGI/
>> >AGFL for that allocation group. Its not clear if this is due to
>> >the EA data on disk pointing to that block, or a bug in the kernel
>> >code. The tools not finding anything suggests to me a kernel bug,
>> >not sure where though...
>> >
>>
>> So what should i do to generate more debug info ?
>
>The absolute ideal from my point of view is a recipe of steps
>which I can follow which is guaranteed to trigger the problem.
>And if this can be trimmed back to a very basic minimum - e.g.
>mkfs (-dsize=something small), a dd command line(s) to fill it
>up so this will trigger, etc, & whatever else...
>
I tried creating a small XFS volume (100MB) in a file , not a
partition, filled it up but it didn't produce any errors. I'll
keep experimenting.
>If I have that recipe and can reproduce it, I can be sure of
>fixing it (and can verify the fix too). The simpler the recipe,
>the better from my point of view.
>
>You seem to be able to reproduce it easily, which is promising.
>
>> Not sure if it helps, but this sequence of events might give a clue :
>
>This is a good start, but is not deterministic between our two
>machines (ie. you hit it but I don't, and theres many variables
>like "heaps of files", and an unknown starting point, etc).
<snip>
>
>Getting closer I think.
>
>cheers.
>
>--
>Nathan
>
>
Scott Fagg <scott.fagg@xxxxxxxxxxx>
Arup Brisbane
(07) 3023 6000
|