From: Patrick Mackinlay <patrick@spacesurfer.com>
To: linux-kernel@vger.kernel.org
Subject: reiserfs problem
Date: Fri, 23 Feb 2001 17:03:40 +0000 [thread overview]
Message-ID: <3A9697EC.892E4230@spacesurfer.com> (raw)
When 2.4.1 was released I reported a kernel oops with reiserfs, I got no
response.
The problem still persists with kernel 2.4.2. I am using mkreiserfs v2
(3.6.25) and tried on different ide hards disks as well as on a software
raid 0 partition, I also tried with and without CONFIG_REISERFS_CHECK
defined, the oops always happens.
My system is a dual pentium 500, 256M memory, IDE:
IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01)
The system has been running flawlessly with 2.2 kernels for months.
This is how I caused the first oops:
Created 2Gig reiserfs partition on /dev/md0 (raid0)
mount /dev/md0 /mnt/md0
Mount took 3-5 seconds
cp -ax / /mnt/md0
Only the /bin directory (not the contents!) was copied and then cp core
dumped. syslog reports an oops, however the system is still usable but
mount/umount/sync is not possible on any filesystems.
kernel oops report:
>>EIP; d2cf9db8 <[reiserfs]create_virtual_node+298/490> <=====
Trace; d2cfc053 <[reiserfs]dc_check_balance_leaf+53/150>
Trace; d2cfc975 <[reiserfs]fix_nodes+115/450>
Trace; d2d062ac <[reiserfs]reiserfs_cut_from_item+1fc/430>
Trace; d2d152f0 <[reiserfs]reiserfs_mounted_fs_count+0/4>
Trace; d2d0686e <[reiserfs]reiserfs_do_truncate+32e/470>
Trace; d2d18044 <.bss.end+1165/???
Trace; d2cf8567 <[reiserfs]reiserfs_truncate_file+b7/1a0>
Trace; d2d0fa24 <[reiserfs].rodata.start+11e4/678e>
Trace; d2d141af <[reiserfs].rodata.start+596f/678e>
Trace; d2cf9382 <[reiserfs]reiserfs_file_release+1d2/380>
Trace; d2cf94cf <[reiserfs]reiserfs_file_release+31f/380>
Trace; d2d0fb8c <[reiserfs].rodata.start+134c/678e>
Trace; d2d141af <[reiserfs].rodata.start+596f/678e>
Trace; c0128230 <file_read_actor+0/60>
Trace; c0135e47 <fput+37/e0>
Trace; c0134d56 <filp_close+a6/b0>
Trace; c0134dbb <sys_close+5b/70>
Trace; c0109127 <system_call+33/38>
Code; d2cf9db8 <[reiserfs]create_virtual_node+298/490>
00000000 <_EIP>:
Code; d2cf9db8 <[reiserfs]create_virtual_node+298/490> <=====
0: 8b 40 14 mov 0x14(%eax),%eax <=====
Code; d2cf9dbb <[reiserfs]create_virtual_node+29b/490>
3: ff d0 call *%eax
Code; d2cf9dbd <[reiserfs]create_virtual_node+29d/490>
5: 89 c2 mov %eax,%edx
Code; d2cf9dbf <[reiserfs]create_virtual_node+29f/490>
7: 8b 06 mov (%esi),%eax
Code; d2cf9dc1 <[reiserfs]create_virtual_node+2a1/490>
9: 83 c4 10 add $0x10,%esp
Code; d2cf9dc4 <[reiserfs]create_virtual_node+2a4/490>
c: 01 c2 add %eax,%edx
Code; d2cf9dc6 <[reiserfs]create_virtual_node+2a6/490>
e: 89 16 mov %edx,(%esi)
Code; d2cf9dc8 <[reiserfs]create_virtual_node+2a8/490>
10: 8b 83 8c 01 00 00 mov 0x18c(%ebx),%eax
--
Patrick Mackinlay patrick@spacesurfer.com
ICQ: 59277981 tel: +44 7050699851
fax: +44 7050699852
SpaceSurfer Limited http://www.spacesurfer.com/
next reply other threads:[~2001-02-23 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 17:03 Patrick Mackinlay [this message]
2001-02-23 18:31 ` reiserfs problem Chris Mason
2001-02-23 18:40 ` Patrick Mackinlay
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=3A9697EC.892E4230@spacesurfer.com \
--to=patrick@spacesurfer.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