From: Christoph Hellwig <hch@infradead.org>
To: Spelic <spelic@shiftmail.org>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-lvm@redhat.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: [linux-lvm] Bugs in mkfs.xfs, device mapper, xfs, and /dev/ram
Date: Thu, 2 Dec 2010 09:17:37 -0500 [thread overview]
Message-ID: <20101202141737.GA29799@infradead.org> (raw)
In-Reply-To: <4CF7A9C4.2040607@shiftmail.org>
On Thu, Dec 02, 2010 at 03:14:28PM +0100, Spelic wrote:
> On 12/02/2010 03:11 PM, Christoph Hellwig wrote:
> >I'm pretty sure you have CONFIG_DEBUG_BLOCK_EXT_DEVT enabled. This
> >option must never be enabled, as it causes block devices to be
> >randomly renumered. Together with the ramdisk driver overloading
> >the BLKFLSBUF ioctl to discard all data it guarantees you to get
> >data loss like yours.
>
> Nope...
>
> # CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
Hmm, I suspect dm-linear's dumb forwarding of ioctls has the same
effect.
next prev parent reply other threads:[~2010-12-02 14:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 13:55 [linux-lvm] Bugs in mkfs.xfs, device mapper, xfs, and /dev/ram Spelic
2010-12-02 14:11 ` Christoph Hellwig
2010-12-02 14:14 ` Spelic
2010-12-02 14:17 ` Christoph Hellwig [this message]
2010-12-02 21:22 ` Mike Snitzer
2010-12-02 22:08 ` Mike Snitzer
2010-12-03 17:11 ` Nick Piggin
2010-12-03 18:15 ` Ted Ts'o
2010-12-02 14:14 ` Spelic
2010-12-02 23:07 ` Dave Chinner
2010-12-03 14:07 ` Spelic
2010-12-06 4:09 ` Dave Chinner
2010-12-06 12:20 ` [linux-lvm] NFS corruption on ENOSPC (was: Re: Bugs in mkfs.xfs, device mapper, xfs, and /dev/ram) Spelic
2010-12-06 13:33 ` Trond Myklebust
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=20101202141737.GA29799@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lvm@redhat.com \
--cc=spelic@shiftmail.org \
--cc=xfs@oss.sgi.com \
/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).