public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Theodore Ts'o <tytso@mit.edu>
Cc: "Hongzhi, Song" <hongzhi.song@windriver.com>,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-block@vger.kernel.org
Subject: Re: Panic with ext4,nbd,qemu-img,block
Date: Thu, 25 Jan 2018 10:26:59 +0100	[thread overview]
Message-ID: <20180125092659.wi2bj3gvv6ezmiuj@quack2.suse.cz> (raw)
In-Reply-To: <20180120234028.GB4451@thunk.org>

On Sat 20-01-18 18:40:28, Theodore Ts'o wrote:
> On Sat, Jan 20, 2018 at 04:41:00PM +0800, Hongzhi, Song wrote:
> > 
> > 329.11 EXT4-fs (nbd0): mounted filesystem with ordered data mode. Opts:
> > (null)
> > 329.12 block nbd0: Connection timed out
> > 329.13 block nbd0: shutting down sockets
> 
> That's your problem.  I'm guessing qemu-nbd is dying for some reason,
> which is causing the nbd device to fail (hence the "connection timed
> out").

All those filesystem errors are obviously his problem but:

329.45 ------------[ cut here ]------------
329.46 kernel BUG at /kernel-source//fs/buffer.c:3091!
329.47 invalid opcode: 0000 [#1] PREEMPT SMP
...

is a kernel problem. Hongzhi, can you please track down which line in
submit_bh_wbc() is line 3091 in your sources? I'd be interested in which
assertion actually failed. My best bets would be on
	BUG_ON(!buffer_mapped(bh));
but I'm not sure...

								Honza

-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

      reply	other threads:[~2018-01-25  9:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-20  8:41 Panic with ext4,nbd,qemu-img,block Hongzhi, Song
2018-01-20 23:40 ` Theodore Ts'o
2018-01-25  9:26   ` Jan Kara [this message]

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=20180125092659.wi2bj3gvv6ezmiuj@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=hongzhi.song@windriver.com \
    --cc=linux-block@vger.kernel.org \
    --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