From: Nicholas Miell <nmiell@attbi.com>
To: linux-kernel@vger.kernel.org
Cc: sct@redhat.com, akpm@digeo.com, adilger@clusterfs.com
Subject: 2.6.0-test1 ext3 slab/fs corruption
Date: 22 Jul 2003 20:45:20 -0700 [thread overview]
Message-ID: <1058931916.1286.9.camel@entropy> (raw)
[-- Attachment #1: Type: text/plain, Size: 2567 bytes --]
I woke up this morning and discovered that a compile had died due to I/O
errors. I found the following in my logs (the rest of the relevant bits
from the log is attached -- 5k bz2, 146k uncompressed). Preempt is on,
htree is in use, e2fsck worked fine.
Jul 21 19:25:32 entropy kernel: EXT3-fs warning (device hda1):
ext3_unlink: Deleting nonexistent file (5632341), 0
Jul 21 19:28:31 entropy kernel: Slab corruption: start=c2a4ba30,
expend=c2a4bbff, problemat=c2a4baa8
Jul 21 19:28:31 entropy kernel: Last user:
[<c584f877>](ext3_destroy_inode+0x17/0x20 [ext3])
Jul 21 19:28:31 entropy kernel: Data:
************************************************************************************************************************6C 13 EC C4 ***************************************************************************************************************************************************************************************************************************************************************************************************************************************************A5
Jul 21 19:28:31 entropy kernel: Next: 71 F0 2C .77 F8 84 C5 A5 C2 0F 17
14 02 C8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Jul 21 19:28:31 entropy kernel: slab error in check_poison_obj(): cache
`ext3_inode_cache': object was modified after freeing
Jul 21 19:28:31 entropy kernel: Call Trace:
Jul 21 19:28:31 entropy kernel: [<c013b33f>]
check_poison_obj+0x13f/0x190
Jul 21 19:28:31 entropy kernel: [<c013ca67>]
kmem_cache_alloc+0x117/0x160
Jul 21 19:28:31 entropy kernel: [<c584f830>] ext3_alloc_inode+0x10/0x40
[ext3]
Jul 21 19:28:31 entropy kernel: [<c584f830>] ext3_alloc_inode+0x10/0x40
[ext3]
Jul 21 19:28:31 entropy kernel: [<c0168909>] alloc_inode+0x19/0x150
Jul 21 19:28:32 entropy kernel: [<c0169336>] new_inode+0x16/0x90
Jul 21 19:28:32 entropy kernel: [<c5847792>] ext3_new_inode+0x42/0x750
[ext3]
Jul 21 19:28:32 entropy kernel: [<c013ca72>]
kmem_cache_alloc+0x122/0x160
Jul 21 19:28:32 entropy kernel: [<c5814442>] new_handle+0x12/0x50 [jbd]
Jul 21 19:28:32 entropy kernel: [<c5814509>] journal_start+0x89/0xb0
[jbd]
Jul 21 19:28:32 entropy kernel: [<c584de0f>] ext3_create+0x3f/0x90
[ext3]
Jul 21 19:28:32 entropy kernel: [<c015edec>] vfs_create+0x7c/0xe0
Jul 21 19:28:32 entropy kernel: [<c015f43f>] open_namei+0x3ef/0x450
Jul 21 19:28:32 entropy kernel: [<c014fc55>] filp_open+0x35/0x60
Jul 21 19:28:32 entropy kernel: [<c015011f>] sys_open+0x3f/0x70
Jul 21 19:28:32 entropy kernel: [<c010aec7>] syscall_call+0x7/0xb
Jul 21 19:28:32 entropy kernel:
[-- Attachment #2: 2.6.0-test1_ext3_slab_corruption.txt.bz2 --]
[-- Type: application/x-bzip, Size: 5154 bytes --]
next reply other threads:[~2003-07-23 3:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 3:45 Nicholas Miell [this message]
2003-07-23 10:14 ` 2.6.0-test1 ext3 slab/fs corruption Alex Tomas
2003-07-23 11:37 ` Alex Tomas
2003-07-26 5:24 ` Nicholas Miell
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=1058931916.1286.9.camel@entropy \
--to=nmiell@attbi.com \
--cc=adilger@clusterfs.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
/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 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.