* Kernel panic when using repacker with reverse order
@ 2004-09-18 0:03 Spam
2004-09-18 15:24 ` Alex Zarochentsev
0 siblings, 1 reply; 9+ messages in thread
From: Spam @ 2004-09-18 0:03 UTC (permalink / raw)
To: reiserfs-list
I got a severe crash when tried the repacker using reverse (1)
order. I did first a normal run:
echo 0 > direction
echo 1 > start
Then I did the reverse:
echo 1 > direction
echo 1 > start
It crashed rather quickly.
Unfortunately I could not capture the whole debug output:
EFLAGS: 00010246 (2.6.9-rc1-mm4)
EIP is at jnode_build_key+0x76/0xc0
eax: c3b3bae0 ebx: 00000000 ecx: 00000000 edx: 0028e000
esi: 0028e000 edi: 00000000 ebp: c3b3bae0 esp: d7581c1c
ds: 007b es: 007b ss: 0068
Process ent:loop0! (pid: 27667, threadinfo=d7580000 task=d758c000)
Stack: d7581c58 d7581c58 00000000 c0c77380 d7581dbc 00000002 c01cb943 d7581e00
c0389ce8 00000000 c01cc401 00000002 c05a7da0 00000000 d7581dd8 c0b25120
00000000 00000105 0000001c 00000000 00000000 00000000 d7581c74 d7581d80
Call Trace:
[<c01cb943>] jnode_lock_parent_coord+0x1b3/0x310
[<c01cc401>] scan_by_coord+0x281/0x320
[<c01cbf7d>] scan_unformatted+0xcd/0x1d0
[<c0138323>] buffered_rmqueue+0x103/0x210
[<c01cbe7f>] scan_common+0x3f/0x50
[<c01cbdd9>] scan_left+0x59/0x90
[<c01c934d>] jnode_flush+0xed/0x3d0
[<c011e047>] tasklet_action+0x37/0x60
[<c01c5bba>] find_first_dirty_jnode+0x2a/0x50
[<c01c9870>] flush_current_atom+0x220/0x2b0
[<c01c640c>] flush_some_atom+0x19c/0x2a0
[<c01da6c9>] entd_flush+0x69/0xf0
[<c0336b77>] schedule+0x237/0x4e0
[<c01da3cc>] entd+0x13c/0x2a0
[<c01da290>] entd+0x0/0x2a0
[<c0101f7d>] kernel_thread_helper+0x5/0x18
Code: 14 8b 83 84 00 00 00 85 c0 75 3b 8d 76 00 8d bc 27 00 00 00 00 89 e8 e8 b9 b5 01 00 89 c3 8b 44 24 04 89 f2 89 f9 89 04 24 89 e8 <ff> 53 54 8b 44 24 04 8b 5c 24 08 8b 74 24 0c 8b 7c 24 10 8b 6c
<6>note: ent:loop0![27667] exited with preempt_count 1
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Kernel panic when using repacker with reverse order
2004-09-18 0:03 Kernel panic when using repacker with reverse order Spam
@ 2004-09-18 15:24 ` Alex Zarochentsev
2004-09-18 15:40 ` Spam
0 siblings, 1 reply; 9+ messages in thread
From: Alex Zarochentsev @ 2004-09-18 15:24 UTC (permalink / raw)
To: Spam; +Cc: reiserfs-list
Hi,
On Sat, Sep 18, 2004 at 02:03:09AM +0200, Spam wrote:
>
> I got a severe crash when tried the repacker using reverse (1)
> order. I did first a normal run:
Thanks for the resport.
Whether reiser4 debug options (assertions) were turned on or off?
>
> echo 0 > direction
> echo 1 > start
>
> Then I did the reverse:
>
> echo 1 > direction
> echo 1 > start
>
> It crashed rather quickly.
> Unfortunately I could not capture the whole debug output:
>
> EFLAGS: 00010246 (2.6.9-rc1-mm4)
> EIP is at jnode_build_key+0x76/0xc0
> eax: c3b3bae0 ebx: 00000000 ecx: 00000000 edx: 0028e000
> esi: 0028e000 edi: 00000000 ebp: c3b3bae0 esp: d7581c1c
> ds: 007b es: 007b ss: 0068
> Process ent:loop0! (pid: 27667, threadinfo=d7580000 task=d758c000)
> Stack: d7581c58 d7581c58 00000000 c0c77380 d7581dbc 00000002 c01cb943 d7581e00
> c0389ce8 00000000 c01cc401 00000002 c05a7da0 00000000 d7581dd8 c0b25120
> 00000000 00000105 0000001c 00000000 00000000 00000000 d7581c74 d7581d80
> Call Trace:
> [<c01cb943>] jnode_lock_parent_coord+0x1b3/0x310
> [<c01cc401>] scan_by_coord+0x281/0x320
> [<c01cbf7d>] scan_unformatted+0xcd/0x1d0
> [<c0138323>] buffered_rmqueue+0x103/0x210
> [<c01cbe7f>] scan_common+0x3f/0x50
> [<c01cbdd9>] scan_left+0x59/0x90
> [<c01c934d>] jnode_flush+0xed/0x3d0
> [<c011e047>] tasklet_action+0x37/0x60
> [<c01c5bba>] find_first_dirty_jnode+0x2a/0x50
> [<c01c9870>] flush_current_atom+0x220/0x2b0
> [<c01c640c>] flush_some_atom+0x19c/0x2a0
> [<c01da6c9>] entd_flush+0x69/0xf0
> [<c0336b77>] schedule+0x237/0x4e0
> [<c01da3cc>] entd+0x13c/0x2a0
> [<c01da290>] entd+0x0/0x2a0
> [<c0101f7d>] kernel_thread_helper+0x5/0x18
> Code: 14 8b 83 84 00 00 00 85 c0 75 3b 8d 76 00 8d bc 27 00 00 00 00 89 e8 e8 b9 b5 01 00 89 c3 8b 44 24 04 89 f2 89 f9 89 04 24 89 e8 <ff> 53 54 8b 44 24 04 8b 5c 24 08 8b 74 24 0c 8b 7c 24 10 8b 6c
> <6>note: ent:loop0![27667] exited with preempt_count 1
>
>
>
--
Alex.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Kernel panic when using repacker with reverse order
2004-09-18 15:24 ` Alex Zarochentsev
@ 2004-09-18 15:40 ` Spam
2004-09-20 7:24 ` Alex Zarochentsev
0 siblings, 1 reply; 9+ messages in thread
From: Spam @ 2004-09-18 15:40 UTC (permalink / raw)
To: Alex Zarochentsev; +Cc: reiserfs-list
Debug options were not turned on. Shall I recompile the kernel with
these on?
I have upgraded to rc2-mm1. I will try the repacker again later
today and see if there is any change.
~S
> Hi,
> On Sat, Sep 18, 2004 at 02:03:09AM +0200, Spam wrote:
>>
>> I got a severe crash when tried the repacker using reverse (1)
>> order. I did first a normal run:
> Thanks for the resport.
> Whether reiser4 debug options (assertions) were turned on or off?
>>
>> echo 0 > direction
>> echo 1 > start
>>
>> Then I did the reverse:
>>
>> echo 1 > direction
>> echo 1 > start
>>
>> It crashed rather quickly.
>> Unfortunately I could not capture the whole debug output:
>>
>> EFLAGS: 00010246 (2.6.9-rc1-mm4)
>> EIP is at jnode_build_key+0x76/0xc0
>> eax: c3b3bae0 ebx: 00000000 ecx: 00000000 edx: 0028e000
>> esi: 0028e000 edi: 00000000 ebp: c3b3bae0 esp: d7581c1c
>> ds: 007b es: 007b ss: 0068
>> Process ent:loop0! (pid: 27667, threadinfo=d7580000 task=d758c000)
>> Stack: d7581c58 d7581c58 00000000 c0c77380 d7581dbc 00000002 c01cb943 d7581e00
>> c0389ce8 00000000 c01cc401 00000002 c05a7da0 00000000 d7581dd8 c0b25120
>> 00000000 00000105 0000001c 00000000 00000000 00000000 d7581c74 d7581d80
>> Call Trace:
>> [<c01cb943>] jnode_lock_parent_coord+0x1b3/0x310
>> [<c01cc401>] scan_by_coord+0x281/0x320
>> [<c01cbf7d>] scan_unformatted+0xcd/0x1d0
>> [<c0138323>] buffered_rmqueue+0x103/0x210
>> [<c01cbe7f>] scan_common+0x3f/0x50
>> [<c01cbdd9>] scan_left+0x59/0x90
>> [<c01c934d>] jnode_flush+0xed/0x3d0
>> [<c011e047>] tasklet_action+0x37/0x60
>> [<c01c5bba>] find_first_dirty_jnode+0x2a/0x50
>> [<c01c9870>] flush_current_atom+0x220/0x2b0
>> [<c01c640c>] flush_some_atom+0x19c/0x2a0
>> [<c01da6c9>] entd_flush+0x69/0xf0
>> [<c0336b77>] schedule+0x237/0x4e0
>> [<c01da3cc>] entd+0x13c/0x2a0
>> [<c01da290>] entd+0x0/0x2a0
>> [<c0101f7d>] kernel_thread_helper+0x5/0x18
>> Code: 14 8b 83 84 00 00 00 85 c0 75 3b 8d 76 00 8d bc 27 00 00
>> 00 00 89 e8 e8 b9 b5 01 00 89 c3 8b 44 24 04 89 f2 89 f9 89 04 24
>> 89 e8 <ff> 53 54 8b 44 24 04 8b 5c 24 08 8b 74 24 0c 8b 7c 24 10 8b
>> 6c
>> <6>note: ent:loop0![27667] exited with preempt_count 1
>>
>>
>>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Kernel panic when using repacker with reverse order
2004-09-18 15:40 ` Spam
@ 2004-09-20 7:24 ` Alex Zarochentsev
2004-09-20 7:46 ` Will Smith
2004-09-20 14:43 ` Spam
0 siblings, 2 replies; 9+ messages in thread
From: Alex Zarochentsev @ 2004-09-20 7:24 UTC (permalink / raw)
To: Spam; +Cc: reiserfs-list
On Sat, Sep 18, 2004 at 05:40:19PM +0200, Spam wrote:
>
> Debug options were not turned on. Shall I recompile the kernel with
> these on?
yes. it gives much more info usually.
> I have upgraded to rc2-mm1. I will try the repacker again later
> today and see if there is any change.
>
> ~S
>
> > Hi,
>
> > On Sat, Sep 18, 2004 at 02:03:09AM +0200, Spam wrote:
> >>
> >> I got a severe crash when tried the repacker using reverse (1)
> >> order. I did first a normal run:
>
> > Thanks for the resport.
>
> > Whether reiser4 debug options (assertions) were turned on or off?
>
> >>
> >> echo 0 > direction
> >> echo 1 > start
> >>
> >> Then I did the reverse:
> >>
> >> echo 1 > direction
> >> echo 1 > start
> >>
> >> It crashed rather quickly.
> >> Unfortunately I could not capture the whole debug output:
> >>
> >> EFLAGS: 00010246 (2.6.9-rc1-mm4)
> >> EIP is at jnode_build_key+0x76/0xc0
> >> eax: c3b3bae0 ebx: 00000000 ecx: 00000000 edx: 0028e000
> >> esi: 0028e000 edi: 00000000 ebp: c3b3bae0 esp: d7581c1c
> >> ds: 007b es: 007b ss: 0068
> >> Process ent:loop0! (pid: 27667, threadinfo=d7580000 task=d758c000)
> >> Stack: d7581c58 d7581c58 00000000 c0c77380 d7581dbc 00000002 c01cb943 d7581e00
> >> c0389ce8 00000000 c01cc401 00000002 c05a7da0 00000000 d7581dd8 c0b25120
> >> 00000000 00000105 0000001c 00000000 00000000 00000000 d7581c74 d7581d80
> >> Call Trace:
> >> [<c01cb943>] jnode_lock_parent_coord+0x1b3/0x310
> >> [<c01cc401>] scan_by_coord+0x281/0x320
> >> [<c01cbf7d>] scan_unformatted+0xcd/0x1d0
> >> [<c0138323>] buffered_rmqueue+0x103/0x210
> >> [<c01cbe7f>] scan_common+0x3f/0x50
> >> [<c01cbdd9>] scan_left+0x59/0x90
> >> [<c01c934d>] jnode_flush+0xed/0x3d0
> >> [<c011e047>] tasklet_action+0x37/0x60
> >> [<c01c5bba>] find_first_dirty_jnode+0x2a/0x50
> >> [<c01c9870>] flush_current_atom+0x220/0x2b0
> >> [<c01c640c>] flush_some_atom+0x19c/0x2a0
> >> [<c01da6c9>] entd_flush+0x69/0xf0
> >> [<c0336b77>] schedule+0x237/0x4e0
> >> [<c01da3cc>] entd+0x13c/0x2a0
> >> [<c01da290>] entd+0x0/0x2a0
> >> [<c0101f7d>] kernel_thread_helper+0x5/0x18
> >> Code: 14 8b 83 84 00 00 00 85 c0 75 3b 8d 76 00 8d bc 27 00 00
> >> 00 00 89 e8 e8 b9 b5 01 00 89 c3 8b 44 24 04 89 f2 89 f9 89 04 24
> >> 89 e8 <ff> 53 54 8b 44 24 04 8b 5c 24 08 8b 74 24 0c 8b 7c 24 10 8b
> >> 6c
> >> <6>note: ent:loop0![27667] exited with preempt_count 1
> >>
> >>
> >>
>
>
--
Alex.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Kernel panic when using repacker with reverse order
2004-09-20 7:24 ` Alex Zarochentsev
@ 2004-09-20 7:46 ` Will Smith
2004-09-20 14:43 ` Spam
1 sibling, 0 replies; 9+ messages in thread
From: Will Smith @ 2004-09-20 7:46 UTC (permalink / raw)
To: Alex Zarochentsev; +Cc: Spam, reiserfs-list
I'm getting a similar thing - a stack trace at least, resulting in
a filesystem that cannot be unmounted.
It only ever comes from running in reverse order. And it's triggered,
for me, *after* the repacker has finished, but during the large flush
of dirty data that the repacker produces.
A workaround, that works for me, seems to be to run a
while true ; do
sync
sleep 10
done
as soon as I start the repacker. My guess is that the repacker triggers
some unusually complex work for the flush() code, showing up an error.
The sync's produce many small flushes rather than 1 large complex one.
Will Smith
Alex Zarochentsev wrote:
> On Sat, Sep 18, 2004 at 05:40:19PM +0200, Spam wrote:
>
>> Debug options were not turned on. Shall I recompile the kernel with
>> these on?
>
>
> yes. it gives much more info usually.
>
>
>> I have upgraded to rc2-mm1. I will try the repacker again later
>> today and see if there is any change.
>>
>> ~S
>>
>>
>>>Hi,
>>
>>>On Sat, Sep 18, 2004 at 02:03:09AM +0200, Spam wrote:
>>>
>>>> I got a severe crash when tried the repacker using reverse (1)
>>>> order. I did first a normal run:
>>
>>>Thanks for the resport.
>>
>>>Whether reiser4 debug options (assertions) were turned on or off?
>>
>>
>>
>>>> echo 0 > direction
>>>> echo 1 > start
>>>>
>>>> Then I did the reverse:
>>>>
>>>> echo 1 > direction
>>>> echo 1 > start
>>>>
>>>> It crashed rather quickly.
>>>> Unfortunately I could not capture the whole debug output:
>>>>
>>>>EFLAGS: 00010246 (2.6.9-rc1-mm4)
>>>>EIP is at jnode_build_key+0x76/0xc0
>>>>eax: c3b3bae0 ebx: 00000000 ecx: 00000000 edx: 0028e000
>>>>esi: 0028e000 edi: 00000000 ebp: c3b3bae0 esp: d7581c1c
>>>>ds: 007b es: 007b ss: 0068
>>>>Process ent:loop0! (pid: 27667, threadinfo=d7580000 task=d758c000)
>>>>Stack: d7581c58 d7581c58 00000000 c0c77380 d7581dbc 00000002 c01cb943 d7581e00
>>>>c0389ce8 00000000 c01cc401 00000002 c05a7da0 00000000 d7581dd8 c0b25120
>>>>00000000 00000105 0000001c 00000000 00000000 00000000 d7581c74 d7581d80
>>>>Call Trace:
>>>>[<c01cb943>] jnode_lock_parent_coord+0x1b3/0x310
>>>>[<c01cc401>] scan_by_coord+0x281/0x320
>>>>[<c01cbf7d>] scan_unformatted+0xcd/0x1d0
>>>>[<c0138323>] buffered_rmqueue+0x103/0x210
>>>>[<c01cbe7f>] scan_common+0x3f/0x50
>>>>[<c01cbdd9>] scan_left+0x59/0x90
>>>>[<c01c934d>] jnode_flush+0xed/0x3d0
>>>>[<c011e047>] tasklet_action+0x37/0x60
>>>>[<c01c5bba>] find_first_dirty_jnode+0x2a/0x50
>>>>[<c01c9870>] flush_current_atom+0x220/0x2b0
>>>>[<c01c640c>] flush_some_atom+0x19c/0x2a0
>>>>[<c01da6c9>] entd_flush+0x69/0xf0
>>>>[<c0336b77>] schedule+0x237/0x4e0
>>>>[<c01da3cc>] entd+0x13c/0x2a0
>>>>[<c01da290>] entd+0x0/0x2a0
>>>>[<c0101f7d>] kernel_thread_helper+0x5/0x18
>>>>Code: 14 8b 83 84 00 00 00 85 c0 75 3b 8d 76 00 8d bc 27 00 00
>>>>00 00 89 e8 e8 b9 b5 01 00 89 c3 8b 44 24 04 89 f2 89 f9 89 04 24
>>>>89 e8 <ff> 53 54 8b 44 24 04 8b 5c 24 08 8b 74 24 0c 8b 7c 24 10 8b
>>>>6c
>>>><6>note: ent:loop0![27667] exited with preempt_count 1
>>>>
>>>>
>>>>
>>
>>
>
--
1400 high resolution textures - http://www.mayang.com/textures
Panoramic travel photos - http://www.willsmith.org/pano
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Kernel panic when using repacker with reverse order
2004-09-20 7:24 ` Alex Zarochentsev
2004-09-20 7:46 ` Will Smith
@ 2004-09-20 14:43 ` Spam
2004-09-20 14:59 ` Alex Zarochentsev
1 sibling, 1 reply; 9+ messages in thread
From: Spam @ 2004-09-20 14:43 UTC (permalink / raw)
To: Alex Zarochentsev; +Cc: reiserfs-list
> On Sat, Sep 18, 2004 at 05:40:19PM +0200, Spam wrote:
>>
>> Debug options were not turned on. Shall I recompile the kernel with
>> these on?
> yes. it gives much more info usually.
>> I have upgraded to rc2-mm1. I will try the repacker again later
>> today and see if there is any change.
I have run several attempts now with the repacker and have not yet
had a error. I am also using the 4k stack patch with this kernel.
~S
>>
>> ~S
>>
>> > Hi,
>>
>> > On Sat, Sep 18, 2004 at 02:03:09AM +0200, Spam wrote:
>> >>
>> >> I got a severe crash when tried the repacker using reverse (1)
>> >> order. I did first a normal run:
>>
>> > Thanks for the resport.
>>
>> > Whether reiser4 debug options (assertions) were turned on or off?
>>
>> >>
>> >> echo 0 > direction
>> >> echo 1 > start
>> >>
>> >> Then I did the reverse:
>> >>
>> >> echo 1 > direction
>> >> echo 1 > start
>> >>
>> >> It crashed rather quickly.
>> >> Unfortunately I could not capture the whole debug output:
>> >>
>> >> EFLAGS: 00010246 (2.6.9-rc1-mm4)
>> >> EIP is at jnode_build_key+0x76/0xc0
>> >> eax: c3b3bae0 ebx: 00000000 ecx: 00000000 edx: 0028e000
>> >> esi: 0028e000 edi: 00000000 ebp: c3b3bae0 esp: d7581c1c
>> >> ds: 007b es: 007b ss: 0068
>> >> Process ent:loop0! (pid: 27667, threadinfo=d7580000 task=d758c000)
>> >> Stack: d7581c58 d7581c58 00000000 c0c77380 d7581dbc 00000002 c01cb943 d7581e00
>> >> c0389ce8 00000000 c01cc401 00000002 c05a7da0 00000000 d7581dd8 c0b25120
>> >> 00000000 00000105 0000001c 00000000 00000000 00000000 d7581c74 d7581d80
>> >> Call Trace:
>> >> [<c01cb943>] jnode_lock_parent_coord+0x1b3/0x310
>> >> [<c01cc401>] scan_by_coord+0x281/0x320
>> >> [<c01cbf7d>] scan_unformatted+0xcd/0x1d0
>> >> [<c0138323>] buffered_rmqueue+0x103/0x210
>> >> [<c01cbe7f>] scan_common+0x3f/0x50
>> >> [<c01cbdd9>] scan_left+0x59/0x90
>> >> [<c01c934d>] jnode_flush+0xed/0x3d0
>> >> [<c011e047>] tasklet_action+0x37/0x60
>> >> [<c01c5bba>] find_first_dirty_jnode+0x2a/0x50
>> >> [<c01c9870>] flush_current_atom+0x220/0x2b0
>> >> [<c01c640c>] flush_some_atom+0x19c/0x2a0
>> >> [<c01da6c9>] entd_flush+0x69/0xf0
>> >> [<c0336b77>] schedule+0x237/0x4e0
>> >> [<c01da3cc>] entd+0x13c/0x2a0
>> >> [<c01da290>] entd+0x0/0x2a0
>> >> [<c0101f7d>] kernel_thread_helper+0x5/0x18
>> >> Code: 14 8b 83 84 00 00 00 85 c0 75 3b 8d 76 00 8d bc 27 00 00
>> >> 00 00 89 e8 e8 b9 b5 01 00 89 c3 8b 44 24 04 89 f2 89 f9 89 04 24
>> >> 89 e8 <ff> 53 54 8b 44 24 04 8b 5c 24 08 8b 74 24 0c 8b 7c 24 10 8b
>> >> 6c
>> >> <6>note: ent:loop0![27667] exited with preempt_count 1
>> >>
>> >>
>> >>
>>
>>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Kernel panic when using repacker with reverse order
2004-09-20 14:43 ` Spam
@ 2004-09-20 14:59 ` Alex Zarochentsev
2004-09-20 15:14 ` Spam
0 siblings, 1 reply; 9+ messages in thread
From: Alex Zarochentsev @ 2004-09-20 14:59 UTC (permalink / raw)
To: Spam; +Cc: reiserfs-list
On Mon, Sep 20, 2004 at 04:43:06PM +0200, Spam wrote:
>
>
> > On Sat, Sep 18, 2004 at 05:40:19PM +0200, Spam wrote:
> >>
> >> Debug options were not turned on. Shall I recompile the kernel with
> >> these on?
>
> > yes. it gives much more info usually.
>
>
> >> I have upgraded to rc2-mm1. I will try the repacker again later
> >> today and see if there is any change.
>
> I have run several attempts now with the repacker and have not yet
> had a error. I am also using the 4k stack patch with this kernel.
does reiser4 work with 4k stack?
> ~S
--
Alex.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Kernel panic when using repacker with reverse order
2004-09-20 14:59 ` Alex Zarochentsev
@ 2004-09-20 15:14 ` Spam
2004-09-20 15:22 ` Spam
0 siblings, 1 reply; 9+ messages in thread
From: Spam @ 2004-09-20 15:14 UTC (permalink / raw)
To: Alex Zarochentsev; +Cc: reiserfs-list
> On Mon, Sep 20, 2004 at 04:43:06PM +0200, Spam wrote:
>>
>>
>> > On Sat, Sep 18, 2004 at 05:40:19PM +0200, Spam wrote:
>> >>
>> >> Debug options were not turned on. Shall I recompile the kernel with
>> >> these on?
>>
>> > yes. it gives much more info usually.
>>
>>
>> >> I have upgraded to rc2-mm1. I will try the repacker again later
>> >> today and see if there is any change.
>>
>> I have run several attempts now with the repacker and have not yet
>> had a error. I am also using the 4k stack patch with this kernel.
> does reiser4 work with 4k stack?
Yes so far. I have run the repacker several times and I have written
and moved a few GB back and forth. No errors yet.
~S
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Kernel panic when using repacker with reverse order
2004-09-20 15:14 ` Spam
@ 2004-09-20 15:22 ` Spam
0 siblings, 0 replies; 9+ messages in thread
From: Spam @ 2004-09-20 15:22 UTC (permalink / raw)
To: Alex Zarochentsev, reiserfs-list
>> On Mon, Sep 20, 2004 at 04:43:06PM +0200, Spam wrote:
>>>
>>>
>>> > On Sat, Sep 18, 2004 at 05:40:19PM +0200, Spam wrote:
>>> >>
>>> >> Debug options were not turned on. Shall I recompile the kernel with
>>> >> these on?
>>>
>>> > yes. it gives much more info usually.
>>>
>>>
>>> >> I have upgraded to rc2-mm1. I will try the repacker again later
>>> >> today and see if there is any change.
>>>
>>> I have run several attempts now with the repacker and have not yet
>>> had a error. I am also using the 4k stack patch with this kernel.
>> does reiser4 work with 4k stack?
Clarification: I used the parse-options-reduce-stack-usage.patch to
enable reiser4 to work with 4k stacks.
> Yes so far. I have run the repacker several times and I have written
> and moved a few GB back and forth. No errors yet.
> ~S
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2004-09-20 15:22 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-09-18 0:03 Kernel panic when using repacker with reverse order Spam
2004-09-18 15:24 ` Alex Zarochentsev
2004-09-18 15:40 ` Spam
2004-09-20 7:24 ` Alex Zarochentsev
2004-09-20 7:46 ` Will Smith
2004-09-20 14:43 ` Spam
2004-09-20 14:59 ` Alex Zarochentsev
2004-09-20 15:14 ` Spam
2004-09-20 15:22 ` Spam
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.