linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Beregalov <a.beregalov@gmail.com>
To: tytso@mit.edu, Alexander Beregalov <a.beregalov@gmail.com>,
	Dmitry Monakhov <dmonakhov@openvz.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-ext4@vger.kernel.org, Jens Axboe <jens.axboe@oracle.com>,
	dmitry.torokhov@gmail.com
Subject: Re: 2.6.33-rc1: kernel BUG at fs/ext4/inode.c:1063 (sparc)
Date: Mon, 28 Dec 2009 02:02:52 +0300	[thread overview]
Message-ID: <a4423d670912271502n13957e8boc168fdc75444dc09@mail.gmail.com> (raw)
In-Reply-To: <20091227225216.GB4429@thunk.org>

2009/12/28  <tytso@mit.edu>:
> On Sun, Dec 27, 2009 at 11:32:25PM +0300, Alexander Beregalov wrote:
>> >> I will try to crosscompile the kernel with Ted's patch on another host.
>>
>> Here is output of 2.6.33-rc2 plus Ted's patch
>>
>> EXT4-fs (sda1): inode #1387643: mdb_free (1) < mdb_claim (2) BUG
>
> OK, can you give me the output of:
>
> debugfs /dev/sda1
> debugfs: stat <1387643>
> debugfs: ncheck 1387643
> debugfs: quit

Cleaning of CCache does not help.

debugfs 1.41.9 (22-Aug-2009)
debugfs:  stat <1387643>
Inode: 1387643   Type: regular    Mode:  0644   Flags: 0x0
Generation: 2004186252    Version: 0x00000000:00000001
User:  1000   Group:  1003   Size: 11028803
File ACL: 0    Directory ACL: 0
Links: 1   Blockcount: 21576
Fragment:  Address: 0    Number: 0    Size: 0
 ctime: 0x4b37d65c:04b0870a -- Mon Dec 28 00:49:16 2009
 atime: 0x4b37d65a:2803e3e5 -- Mon Dec 28 00:49:14 2009
 mtime: 0x4b37d65c:04b0870a -- Mon Dec 28 00:49:16 2009
crtime: 0x5ad6374b:2803e3e5 -- Tue Apr 17 22:04:59 2018
Size of extra inode fields: 28
BLOCKS:
(0-11):172032-172043, (IND):165412, (12-1035):172044-173067,
(DIND):165380, (IND):165381, (1036-2047):173068-174079,
(2048-2059):188416-188427, (IND):165414, (2060-2692):188428-189060
TOTAL: 2697

debugfs:  ncheck 1387643
Inode   Pathname
1387643 /home/alexb/linux-2.6/kernel/built-in.o


~/linux-2.6 $ rm kernel/built-in.o
~/linux-2.6 $ sync
~/linux-2.6 $ kmake
  CHK     include/linux/version.h
  CHK     include/generated/utsrelease.h
  CALL    scripts/checksyscalls.sh
  CHK     include/generated/compile.h
  LD      kernel/built-in.o
  LD [M]  fs/btrfs/btrfs.o
fs/btrfs/relocation.o: file not recognized: File truncated

  reply	other threads:[~2009-12-27 23:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-24 22:28 2.6.33-rc1: kernel BUG at fs/ext4/inode.c:1063 (sparc) Alexander Beregalov
2009-12-24 22:49 ` Alexander Beregalov
2009-12-25 12:31   ` Dmitry Monakhov
2009-12-25 19:33     ` Alexander Beregalov
2009-12-25 23:47       ` Dmitry Monakhov
2009-12-27 20:32         ` Alexander Beregalov
2009-12-27 21:38           ` Dmitry Torokhov
2009-12-27 22:52           ` tytso
2009-12-27 23:02             ` Alexander Beregalov [this message]
2009-12-28  3:51               ` tytso
2009-12-30  5:37                 ` tytso
2009-12-30 13:18                   ` Dmitry Monakhov
2009-12-30 17:45                     ` tytso
2009-12-30 17:48                     ` tytso
2009-12-24 23:05 ` tytso
2009-12-24 23:15   ` tytso

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=a4423d670912271502n13957e8boc168fdc75444dc09@mail.gmail.com \
    --to=a.beregalov@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dmonakhov@openvz.org \
    --cc=jens.axboe@oracle.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).