All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Walter <linux@stwm.de>
To: Ext4 Developers List <linux-ext4@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: JBD2: Spotted dirty metadata buffer....
Date: Mon, 21 Nov 2016 16:28:03 +0100	[thread overview]
Message-ID: <1744886.OgPgGFoXj7@stwm.de> (raw)

Hello,

I'm testing EXT4 with an external journal (data=journal). When writing I rather often get

	JBD2: Spotted dirty metadata buffer (dev = dm-22, blocknr = 1008028301). There's a risk of filesystem corruption in case of system crash.

Now other message is logged. If I unmount the filesystem an do an forced fsck, all seems fine.

The filesystem as it's journal are on a LV (which is again backed by DRBD). The journal, too.

Im using stable kernel 4.8.8.

I created the journal with:

	mkfs.ext4 -O journal_dev -v -b 4096  -L jdyn /dev/export/jdyn

I created the filesystem with:

	mkfs.ext4 -J device=UUID=625d871f-c278-4acb-916d-774dc78dbd8a -v -b 4096 -E stride=$((512/4)),stripe_width=$((512/4*3)),lazy_itable_init=0,nodiscard -O inline_data,mmp -L dyn /dev/export/dyn


I tested it also with data=writeback. I didn't see these errors then.

Regards,
-- 
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts

             reply	other threads:[~2016-11-21 15:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-21 15:28 Wolfgang Walter [this message]
2016-11-22  0:49 ` JBD2: Spotted dirty metadata buffer Andreas Dilger
2016-11-22 13:56   ` Wolfgang Walter
2016-11-22 23:02     ` Andreas Dilger
     [not found] ` <11848279.gFnWiZMlh7@stwm.de>
     [not found]   ` <6EBBE85C-8A87-4D8B-9897-3D67D4B6D732@dilger.ca>
2016-11-28 11:26     ` Wolfgang Walter
2017-09-06 12:46       ` Wolfgang Walter
2017-09-06 18:07         ` Andreas Dilger

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=1744886.OgPgGFoXj7@stwm.de \
    --to=linux@stwm.de \
    --cc=linux-ext4@vger.kernel.org \
    --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 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.