From: Eric Sandeen <sandeen@redhat.com>
To: Andre Noll <maan@systemlinux.org>
Cc: Bernd Schubert <bernd.schubert@fastmail.fm>,
Andrew Vasquez <andrew.vasquez@qlogic.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
Linux Driver <Linux-Driver@qlogic.com>,
Thomas Helle <Helle@tuebingen.mpg.de>
Subject: Re: ext4: (2.6.34-rc4): This should not happen!! Data will be lost
Date: Tue, 20 Apr 2010 11:51:11 -0500 [thread overview]
Message-ID: <4BCDDB7F.6040903@redhat.com> (raw)
In-Reply-To: <20100420153723.GE25507@skl-net.de>
On 04/20/2010 10:37 AM, Andre Noll wrote:
...
> - device timeout 30s, nobarrier
> No problem at all, all three runs OK.
>
> Eric, are you still interested in seeing the blktrace output? Suppose,
> I should use a 30s timeout, nodealloc and barriers=1 as this triggers
> the problem within minutes.
Hm, so something about barriers being issued is causing timeout
problems on the device...?
since nodelalloc made it -worse- I suppose that rules out the problems
with fs flushing near ensopc, that should only be happening with delalloc.
To be honest I'm not sure what I would do with the blktrace data now,
but perhaps someone might be interested to see it; I'd at least gather it.
-Eric
next prev parent reply other threads:[~2010-04-20 17:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 12:35 ext4: (2.6.34-rc4): This should not happen!! Data will be lost Andre Noll
2010-04-16 14:29 ` tytso
2010-04-16 15:02 ` Eric Sandeen
2010-04-16 15:30 ` Andre Noll
2010-04-16 15:43 ` Eric Sandeen
2010-04-16 15:52 ` Andrew Vasquez
2010-04-16 16:08 ` Andre Noll
2010-04-16 16:36 ` Andrew Vasquez
2010-04-16 17:07 ` Andre Noll
2010-04-17 16:55 ` Bernd Schubert
2010-04-17 18:19 ` Andre Noll
2010-04-17 18:43 ` Bernd Schubert
2010-04-17 20:45 ` Eric Sandeen
2010-04-17 22:38 ` Andre Noll
2010-04-20 15:37 ` Andre Noll
2010-04-20 16:51 ` Eric Sandeen [this message]
2010-04-20 17:26 ` Bernd Schubert
2010-04-20 18:35 ` Andre Noll
2010-04-20 20:09 ` Bernd Schubert
2010-04-20 17:46 ` Andre Noll
2010-04-22 8:21 ` Andre Noll
2010-04-21 8:57 ` Dmitry Monakhov
2010-04-21 13:47 ` Andre Noll
2010-04-16 15:57 ` Andre Noll
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=4BCDDB7F.6040903@redhat.com \
--to=sandeen@redhat.com \
--cc=Helle@tuebingen.mpg.de \
--cc=Linux-Driver@qlogic.com \
--cc=andrew.vasquez@qlogic.com \
--cc=bernd.schubert@fastmail.fm \
--cc=linux-ext4@vger.kernel.org \
--cc=maan@systemlinux.org \
/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.