From: Chris Mason <chris.mason@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Warning: bad fsid on block 20971520
Date: Wed, 11 Jan 2012 11:37:14 -0500 [thread overview]
Message-ID: <20120111163714.GE2179@shiny> (raw)
In-Reply-To: <20120111154621.GX7322@twin.jikos.cz>
On Wed, Jan 11, 2012 at 04:46:21PM +0100, David Sterba wrote:
> Hi,
>
> the $subj warning appears sometimes in syslog, in my case when
> xfstests/209 runs looped. The minimal reproducer is looped mkfs+mount.
I've been seeing this as well. It's new with 3.2, and I haven't yet
been able to track it down.
The first thing that happens when we mount the FS is a block layer
invalidate, and that must be dropping the write.
It's also possible (but very unlikely) that mkfs.btrfs is neglecting to
write that block.
Do you have a reliable way to reproduce? If so, can you try with a much
older mkfs.btrfs.
-chris
next prev parent reply other threads:[~2012-01-11 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 15:46 Warning: bad fsid on block 20971520 David Sterba
2012-01-11 16:37 ` Chris Mason [this message]
2012-01-11 22:34 ` David Sterba
2012-01-11 22:54 ` Chris Mason
2012-01-16 14:34 ` David Sterba
2012-01-16 18:36 ` David Sterba
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=20120111163714.GE2179@shiny \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@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 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).