From: Yaroslav Halchenko <yoh@onerussian.com>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: buffer layer error at fs/buffer.c:431
Date: Mon, 1 Sep 2003 18:41:29 -0400 [thread overview]
Message-ID: <20030901224129.GA12834@washoe.rutgers.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2340 bytes --]
Dear Kernel People,
Installed fresh kernel 2.6.0-test4-bk3 and have got problem after about
2 hours of work
Sep 1 16:47:14 localhost kernel: buffer layer error at fs/buffer.c:431
Sep 1 16:47:14 localhost kernel: Call Trace:
Sep 1 16:47:14 localhost kernel: [__find_get_block_slow+148/304] __find_get_block_slow+0x94/0x130
Sep 1 16:47:14 localhost kernel: [__mark_inode_dirty+231/240] __mark_inode_dirty+0xe7/0xf0
Sep 1 16:47:14 localhost kernel: [__find_get_block+145/240] __find_get_block+0x91/0xf0
Sep 1 16:47:14 localhost kernel: [ext3_clear_blocks+248/352] ext3_clear_blocks+0xf8/0x160
Sep 1 16:47:14 localhost kernel: [ext3_free_data+152/336] ext3_free_data+0x98/0x150
Sep 1 16:47:14 localhost kernel: [ext3_free_branches+230/624] ext3_free_branches+0xe6/0x270
Sep 1 16:47:14 localhost kernel: [ext3_truncate+1294/1552] ext3_truncate+0x50e/0x610
Sep 1 16:47:14 localhost kernel: [vmtruncate+166/336] vmtruncate+0xa6/0x150
Sep 1 16:47:14 localhost kernel: [inode_setattr+358/400] inode_setattr+0x166/0x190
Sep 1 16:47:14 localhost kernel: [ext3_setattr+120/384] ext3_setattr+0x78/0x180
Sep 1 16:47:14 localhost kernel: [notify_change+334/400] notify_change+0x14e/0x190
Sep 1 16:47:14 localhost kernel: [do_truncate+75/112] do_truncate+0x4b/0x70
Sep 1 16:47:14 localhost kernel: [dput+48/528] dput+0x30/0x210
Sep 1 16:47:14 localhost kernel: [permission+44/80] permission+0x2c/0x50
Sep 1 16:47:14 localhost kernel: [may_open+368/464] may_open+0x170/0x1d0
Sep 1 16:47:14 localhost kernel: [open_namei+168/1024] open_namei+0xa8/0x400
Sep 1 16:47:14 localhost kernel: [filp_open+62/112] filp_open+0x3e/0x70
Sep 1 16:47:14 localhost kernel: [sys_open+91/144] sys_open+0x5b/0x90
Sep 1 16:47:14 localhost kernel: [syscall_call+7/11] syscall_call+0x7/0xb
Sep 1 16:47:14 localhost kernel:
Sep 1 16:47:14 localhost kernel: block=827392, b_blocknr=4294967295
Details of kernel configuration and dmesg is at
http://www.onerussian.com/Linux/bug.buffer/
Thank you!
.-.
=------------------------------ /v\ ----------------------------=
Keep in touch // \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User ^^-^^ [175555]
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2003-09-01 22:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030901224129.GA12834@washoe.rutgers.edu \
--to=yoh@onerussian.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;
as well as URLs for NNTP newsgroup(s).