All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@redhat.com>
To: Daniel Poelzleithner <poelzi@poelzi.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: flush-btrfs-1 hangs when building openwrt
Date: Tue, 25 Jan 2011 10:30:56 -0500	[thread overview]
Message-ID: <20110125153055.GA2598@localhost.localdomain> (raw)
In-Reply-To: <4D3E8EF5.1050008@poelzi.org>

On Tue, Jan 25, 2011 at 09:51:01AM +0100, Daniel Poelzleithner wrote:
> Hi,
> 
> Since update to 2.6.37 I can't build openwrt on my btrfs buildroot anymore.
> I'm not sure if this is related to the other flush-btrfs-1 thread.
> 
> plenty of diskspace is free:
> 
> /dev/mapper/cruor-build
>                        97G   68G   27G  73% /opt/build
> 
> It always hangs when openwrt builds the ext4 image and runs tune2fs on it.
> 
> /opt/build/fahrenheit/openwrt/staging_dir/host/bin/tune2fs -O
> extents,uninit_bg,dir_index
> /opt/build/fahrenheit/openwrt/build_dir/linux-x86_kvm_guest/root.ext4
> tune2fs 1.41.13 (13-Dec-2010)
> 
> the processes can't be killed.
> 
> alt-sysctl-t does not show anything, nor is there a oops.
> 
> I put the the openwrt config I'm using at https://gist.github.com/794593
> , maybe it is reproduceable.
> 
> Linux cruor 2.6.37 #2 SMP Thu Jan 20 02:09:59 CET 2011 x86_64 GNU/Linux
> 

How about sysrq+w when it's hanging.  Also could you give the exact steps to
reproduce?  I went to the openwrt site to try and build, but it seems like
theres alot of moving parts.  If you can just tell me what to download and what
you run to reproduce I can try and reproduce locally.  Thanks,

Josef

  reply	other threads:[~2011-01-25 15:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25  8:51 flush-btrfs-1 hangs when building openwrt Daniel Poelzleithner
2011-01-25 15:30 ` Josef Bacik [this message]
2011-01-25 21:16   ` Daniel Poelzleithner
2011-01-31 10:52 ` Sander
2011-01-31 11:08   ` cwillu
2011-01-31 11:18     ` Sander
2011-01-31 11:26       ` cwillu
2011-01-31 11:40         ` Sander

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=20110125153055.GA2598@localhost.localdomain \
    --to=josef@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=poelzi@poelzi.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 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.