From: Theodore Ts'o <tytso@mit.edu>
To: Andrey Sidorov <qrxd43@motorola.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: A warning from 3.6+ with bigalloc and delalloc when running xfstest
Date: Sat, 13 Oct 2012 22:18:34 -0400 [thread overview]
Message-ID: <20121014021834.GA4418@thunk.org> (raw)
In-Reply-To: <CAA0+VHySFTOC53QGyt2aCk4vNq45dcfptEHN0vc+tLnZA0tgng@mail.gmail.com>
On Sat, Oct 13, 2012 at 02:29:48PM -0400, Andrey Sidorov wrote:
> I didn't see it as well, but wanted to be sure it won't break file
> system once occurred.
> Our use-case is mostly dio and pre-fallocated writes, so I think we'll be fine.
> Thanks!
Yes, that will work just fine. That in fact was the use case I was
primarily interested in when I did the bigalloc work. The main
weaknesses come from using buffered writes with delayed allocation and
when the disk is almost full.
- Ted
prev parent reply other threads:[~2012-10-14 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 14:59 A warning from 3.6+ with bigalloc and delalloc when running xfstest Zheng Liu
[not found] ` <20121009054820.GA8028@thunk.org>
2012-10-09 6:29 ` Zheng Liu
2012-10-09 13:51 ` Theodore Ts'o
2012-10-10 17:02 ` Andrey Sidorov
2012-10-11 15:57 ` Zheng Liu
2012-10-13 18:29 ` Andrey Sidorov
2012-10-14 2:18 ` Theodore Ts'o [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=20121014021834.GA4418@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=qrxd43@motorola.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.