xfs
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: Bugs in mkfs.xfs, device mapper, xfs, and /dev/ram

from [Spelic] [Permanent Link][Original]
To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: Bugs in mkfs.xfs, device mapper, xfs, and /dev/ram
From: Spelic <spelic@xxxxxxxxxxxxx>
Date: Thu, 02 Dec 2010 15:14:28 +0100
Cc: "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, linux-lvm@xxxxxxxxxx
In-reply-to: <20101202141134.GA22012@xxxxxxxxxxxxx>
References: <4CF7A539.1050206@xxxxxxxxxxxxx> <20101202141134.GA22012@xxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.11) Gecko/20100713 Thunderbird/3.0.6 
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
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: Bugs in mkfs.xfs, device mapper, xfs, and /dev/ram, Christoph Hellwig
Next by Date:  Re: Bugs in mkfs.xfs, device mapper, xfs, and /dev/ram, Spelic
Previous by Thread:  Re: Bugs in mkfs.xfs, device mapper, xfs, and /dev/ram, Christoph Hellwig
Next by Thread:  Re: Bugs in mkfs.xfs, device mapper, xfs, and /dev/ram, Christoph Hellwig
Indexes:  [Date] [Thread] [Top] [All Lists]