From: " ÍõÀèÃ÷ " <firetiger977@163.com>
To: linux-kernel@vger.kernel.org
Subject: RE: OOPS: reiserfs panic
Date: Fri, 2 Nov 2001 22:45:20 +0800 (CST) [thread overview]
Message-ID: <3BE2B180.28918@bj221.163.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2299 bytes --]
RedHat 7.2 shipped with kernel 2.4.7.
I have tried the 2.4.14-pre7, panic too.
/var/log/messages:
Nov 3 17:35:32 localhost kernel: vs-5150: search_by_key: invalid format
found in block 20795. Fsck?
Nov 3 17:35:32 localhost kernel: vs-13050: reiserfs_update_sd: i/o failure
occurred trying to update [44468 44476 0x0 SD] stat data<4>is_leaf: item
location seems wrong (second one): *NEW* [44468 44474 0x0 SD], item_len 44,
item_location 4084, free_space(entry_count) 65535
fdisk output:
Disk /dev/hda: 255 heads, 63 sectors, 5005 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 383 3076416 b Win95 FAT32
/dev/hda2 384 893 4096575 7 HPFS/NTFS
/dev/hda3 * 894 912 152617+ 83 Linux
/dev/hda4 913 5005 32877022+ f Win95 Ext'd (LBA)
/dev/hda5 913 1422 4096543+ 7 HPFS/NTFS
/dev/hda6 1423 2442 8193118+ b Win95 FAT32
/dev/hda7 2443 3717 10241406 b Win95 FAT32
/dev/hda8 3718 4227 4096543+ 83 Linux
/dev/hda9 4228 4278 409626 82 Linux swap
/dev/hda10 4279 5005 5839596 83 Linux
The reiserfs created at hda10.
3.x.0k-pre10
mkreiserfs /dev/hda10 display:
mkreiserfs: Guessing about desired format..
mkreiserfs: Kernel 2.4.14-pre7 is running.
13107k will be used
Block 16 (0x30a) contains super block of format 3.6 with standart journal
Block count: 1459899
Bitmap number: 45
Blocksize: 4096
Free blocks: 1451643
Root block: 8211
Tree height: 2
Hash function used to sort names: "r5"
Objectid map size 2, max 972
Journal parameters:
Device [0x0]
Magic [0x527942af]
Size 8193 (including journal header) (first block 18)
Max transaction length 1024
Max batch size 900
Max commit age 30
Spase reserved by journal: 0
Correctness checked after mount 1
Fsck field 0x0
=============================================================
http://dating.163.com ÇãÐĵÄÔ¼»á¶ÔÏó£¬ÍêÈ«¿ÉÒÔÕâÀïÕÆÎÕ£¡
http://sms.163.com ÃÀºÃµÄ¸ÐÇéÔÚÓÚ²»¶ÏµÄÁªÏµ£¡
http://stock.163.com ½â¹ÉÊз³ÄÕ£¬´ò¿ª²Æ¸»Ö®ÃÅÓÉ´Ë¿ªÊ¼ ...
next reply other threads:[~2001-11-02 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-02 14:45 ÍõÀèÃ÷ [this message]
[not found] <3BE2A84C.E072AD98@namesys.com>
2001-11-03 18:20 ` OOPS: reiserfs panic firetiger
-- strict thread matches above, loose matches on Subject: below --
2001-11-02 3:18 firetiger
2001-11-02 12:46 ` Hans Reiser
2001-11-02 13:19 ` Rik van Riel
2001-11-02 13:19 ` Chris Mason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BE2B180.28918@bj221.163.com \
--to=firetiger977@163.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox