From: Theodore Ts'o <tytso@mit.edu>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: mkfs.ext4 -D option fails to mount
Date: Thu, 29 Jun 2017 13:53:19 -0400 [thread overview]
Message-ID: <20170629175319.s75rdncvejil357p@thunk.org> (raw)
In-Reply-To: <20170629155727.GA8536@linux.intel.com>
On Thu, Jun 29, 2017 at 09:57:27AM -0600, Ross Zwisler wrote:
> On Thu, Jun 29, 2017 at 09:35:38AM -0600, Ross Zwisler wrote:
> > Our validation team noticed that in some configurations mkfs.ext4 with the
> > -D option creates a filesystem that can't be mounted:
The -D option just means that we're doing the I/O using Direct I/O (as
opposed to buffered I/O). It shouldn't make any difference to what
gets written, so this very much smells like a bug in how /dev/pmem
supports Direct I/O...
> One more bit of info - this seems to be strongly tied to the size of the
> block device. With a 32 GB block device it works fine, with 248 GB you get
> overlap messages for groups 1 through 63, and with a 250 GB device you get
> overlaps for groups 1 through 1999.
This very much sounds like Direct I/O is just getting completely
botched for the pmem device, and writes to a block group descriptor
block is affecting the wrong place on the storage device.
- Ted
next prev parent reply other threads:[~2017-06-29 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 15:35 mkfs.ext4 -D option fails to mount Ross Zwisler
2017-06-29 15:57 ` Ross Zwisler
2017-06-29 17:53 ` Theodore Ts'o [this message]
2017-06-29 23:06 ` Ross Zwisler
2017-06-29 23:48 ` Theodore Ts'o
2017-06-30 17:47 ` Ross Zwisler
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=20170629175319.s75rdncvejil357p@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=ross.zwisler@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.