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

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

from [Christoph Hellwig] [Permanent Link][Original]
To: Spelic <spelic@xxxxxxxxxxxxx>
Subject: Re: Bugs in mkfs.xfs, device mapper, xfs, and /dev/ram
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 2 Dec 2010 09:11:34 -0500
Cc: "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, linux-lvm@xxxxxxxxxx
In-reply-to: <4CF7A539.1050206@xxxxxxxxxxxxx>
References: <4CF7A539.1050206@xxxxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15) 
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.
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Bugs in mkfs.xfs, device mapper, xfs, and /dev/ram, Spelic
Next by Date:  Re: Bugs in mkfs.xfs, device mapper, xfs, and /dev/ram, Spelic
Previous by Thread:  Bugs in mkfs.xfs, device mapper, xfs, and /dev/ram, Spelic
Next by Thread:  Re: Bugs in mkfs.xfs, device mapper, xfs, and /dev/ram, Spelic
Indexes:  [Date] [Thread] [Top] [All Lists]