From: Alexander Beregalov <a.beregalov@gmail.com>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org, Jens Axboe <jens.axboe@oracle.com>,
"Theodore Ts'o" <tytso@mit.edu>
Subject: Re: 2.6.33-rc1: kernel BUG at fs/ext4/inode.c:1063 (sparc)
Date: Fri, 25 Dec 2009 22:33:05 +0300 [thread overview]
Message-ID: <a4423d670912251133u795338a4wd32d5cdef8c36c75@mail.gmail.com> (raw)
In-Reply-To: <87hbrfdylc.fsf@openvz.org>
>> It seems I can easily reproduce it.
>> But I can't compile 2.6.33-rc2 :)
>>
>> scripts/kconfig/conf -s arch/sparc/Kconfig
>> CHK include/linux/version.h
>> CHK include/generated/utsrelease.h
>> CALL scripts/checksyscalls.sh
>> CHK include/generated/compile.h
>> GZIP kernel/config_data.gz
>> CC fs/configfs/inode.o
>> IKCFG kernel/config_data.h
>> LD [M] fs/btrfs/btrfs.o
>> CC kernel/configs.o
>> fs/btrfs/sysfs.o: file not recognized: File truncated
> This happens because of delayed allocation. Each time BUG or
> unexpected power off happens during object files usually becomes
> broken. IMHO this is expected issue. Just recompile from beginning
> # make clean; make -j4
It does not help, it still fails.
I will try to crosscompile the kernel with Ted's patch on another host.
> As soon as your testcase is kernel compilation.
> Strange i'm living with quota patches on my notebook more than
> a month( two weeks with the version committed to quota git tree)
> with and without quota . But this never happens.
> Currently i'm trying to reproduce the bug on 2.6.33-rc2
> Please add keep me in cc because seems the bug was introduced
> (or just triggered) by my quota patches.
>> make[2]: *** [fs/btrfs/btrfs.o] Error 1
>> make[1]: *** [fs/btrfs] Error 2
>> make[1]: *** Waiting for unfinished jobs....
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-12-25 19:33 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 [this message]
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
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=a4423d670912251133u795338a4wd32d5cdef8c36c75@mail.gmail.com \
--to=a.beregalov@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).