On 3/11/07, Edward Shishkin <[EMAIL PROTECTED]> wrote:
Hello Matheus,
Unfortunately, there is no suggestions except checking this by fsck.
Thanks,
Edward.
Just did it, here is what i got:
FSCK: Node (3112), item (12), [123c7:1(SD):12e747561726567:5a379:0]: item has
the wrong length (56). Sho
Hello Matheus,
Unfortunately, there is no suggestions except checking this by fsck.
Thanks,
Edward.
Matheus Izvekov wrote:
Got this oops message while using reiser4:
reiser4[q(3866)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[q(3866)]:
Got this oops message while using reiser4:
reiser4[q(3866)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[q(3866)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]:
WARNING: Keys are inconsistent. Fsck?
reiser4[q(3866)]: cbk_level_lookup (
Devils-Hawk wrote:
The problem still persists also trying to boot multiple times it
sometimes triggers much earlier in the boot process than it did before.
Hmm.. can not reproduce it..
The attached patch (against reiser4-for-2.6[19, 20]) allows to dump stack
and some useful info noted as edw
The problem still persists also trying to boot multiple times it
sometimes triggers much earlier in the boot process than it did before.
regards devh
Edward Shishkin wrote:
Would you please try the attached patch over reiser4-for-2.6.[19, 20]
Thanks,
Edward.
Devils-Hawk wrote:
Recently tried switching from 2.6.18 + reiser4-for-2.6.18-r3.patch.gz,
which works perfectly fine to 2.6.19 + reiser4-for-2.6.19-r3.patch.gz
I also tried 2.6.20 laurent riffard's reiser4-for-2.6.20. The last
both die somewhere during init when one of the 2 following asserts f
Devils-Hawk wrote:
Recently tried switching from 2.6.18 + reiser4-for-2.6.18-r3.patch.gz,
which works perfectly fine to 2.6.19 + reiser4-for-2.6.19-r3.patch.gz
I also tried 2.6.20 laurent riffard's reiser4-for-2.6.20. The last
both die somewhere during init when one of the 2 following asserts f
Recently tried switching from 2.6.18 + reiser4-for-2.6.18-r3.patch.gz,
which works perfectly fine to 2.6.19 + reiser4-for-2.6.19-r3.patch.gz
I also tried 2.6.20 laurent riffard's reiser4-for-2.6.20. The last both
die somewhere during init when one of the 2 following asserts fails:
extent_file_op
Jonathan Briggs wrote:
On Thu, 2004-03-25 at 04:32, Nikita Danilov wrote:
Jonathan Briggs writes:
> The system is running Linux kernel 2.6.5-rc2. It's tainted by Nvidia
> drivers.
>
> The system was compiling the kernel, and Reiser4 panicked.
Was compilation multi-threaded (make -j)?
No
The system is running Linux kernel 2.6.5-rc2. It's tainted by Nvidia
drivers.
The system was compiling the kernel, and Reiser4 panicked.
The Reiser4 panic starts at line 443 of the attached dmesg log.
The Reiser4 filesystem is on a MD RAID 0 device made of two SCSI disks.
I had some Re
10 matches
Mail list logo