From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0b-00082601.pphosted.com ([67.231.153.30]:46234 "EHLO mx0b-00082601.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751788AbcAOUKC (ORCPT ); Fri, 15 Jan 2016 15:10:02 -0500 Subject: Re: crashblk: a block device crash emulator. To: Takashi HOSHINO , Andreas Dilger References: <5696FEED.1080604@labs.cybozu.co.jp> <5698957C.8010508@labs.cybozu.co.jp> CC: linux-fsdevel , , From: Josef Bacik Message-ID: <56995210.2000201@fb.com> Date: Fri, 15 Jan 2016 15:09:52 -0500 MIME-Version: 1.0 In-Reply-To: <5698957C.8010508@labs.cybozu.co.jp> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On 01/15/2016 01:45 AM, Takashi HOSHINO wrote: > Hi Andreas, > > On 2016/01/15 4:44, Andreas Dilger wrote: >> On Jan 13, 2016, at 6:50 PM, Takashi HOSHINO >> wrote: >>> >>> Hi all, >>> >>> I'm developing 'crashblk'. >>> It is a memory block device driver to emulate crash, IO error, >>> and various response time. >> >> Why not use/improve dm-flakey for this, rather than making yet another >> device that does something similar? > > I did not know dm-flakey until your reply. Thank you. > > I read its documents and code a bit. > The big purpose of two projects are the same, which is to test software > on block devices with errors, but their functions are almost different. > > It may be nice idea to implement alternative implementation of crashblk > on device-mapper version by someone. > Currently I'm not familiar with device-mapper development, and I do not > have any motivation with it. > There's also dm-log-writes which will log writes to an external journal to allow you to replay writes and verify the fs is consistent at all steps of operation. Thanks, Josef