Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Sitsofe Wheeler <sitsofe@gmail.com>, David Nellans <david@nellans.org>
Cc: Nan WANG <wangnan@cnnic.cn>, "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Urgent problem while using Fio to test random write performance
Date: Thu, 21 May 2015 19:07:49 -0600	[thread overview]
Message-ID: <555E8165.6070608@kernel.dk> (raw)
In-Reply-To: <CALjAwxjz2qXivBru2HEch3Rsg_40rmZMvmD-fVknz6Ny1mrqqA@mail.gmail.com>

On 05/21/2015 02:39 PM, Sitsofe Wheeler wrote:
> On 21 May 2015 at 15:22, David Nellans <david@nellans.org> wrote:
>> you're randwrite to a raw partition. if you had a filesystem on that
>> partition you were trying to use, then well, your data is gone/corrupted.
>> without a filesystem on it, i'm not sure how you'd think that your disc
>> usage has become "100%" without some xgui widgit warning you, so seems
>> likely you did something you didn't mean to with regards to writing to
>> /dev/sdb1 directly
>>
>> if you use fio on devices/partitions with a filesystem, you need to have it
>> write to files or it will trash your filesystem
>
> It's unlikely but it wasn't mentioned which partition became 100%
> full. You should also make sure that /dev/sdb1 really exists as a
> block device (e.g. via using file) otherwise you'll make/fill a
> standard file called /dev/sdb1 .

That's true, though on modern systems that will fail since /dev is 
mounted on devtmpfs which doesn't support O_DIRECT. In general, 
allow_file_create=0 can be used to turn off file creation if you expect 
to run on block devices. This can avoid problems like this.


-- 
Jens Axboe



      reply	other threads:[~2015-05-22  1:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21  8:17 Urgent problem while using Fio to test random write performance Nan WANG
2015-05-21 14:22 ` David Nellans
2015-05-21 20:39   ` Sitsofe Wheeler
2015-05-22  1:07     ` Jens Axboe [this message]

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=555E8165.6070608@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=david@nellans.org \
    --cc=fio@vger.kernel.org \
    --cc=sitsofe@gmail.com \
    --cc=wangnan@cnnic.cn \
    /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