From: Fredrik Andersson <nablaman@gmail.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Fwd: Ext4 bug with fallocate
Date: Tue, 27 Oct 2009 09:17:03 +0100 [thread overview]
Message-ID: <a125a870910270117qa90debp8d5a9f90ffb8434@mail.gmail.com> (raw)
In-Reply-To: <4AE67A1B.8060704@redhat.com>
> Not trying to ignore you, but trying to sort out some corruption issues that
> I'm afraid I have to rank higher than a hang for now...
I understand. Good to know someone is thinking about it anyway :-)
>
> From the traces, things are hung up on the i_data_sem; several pdflushes
> want it for read in ext4_get_blocks_wrap, and drbdmakes presumably have it
> downed for write in ext4_ext_truncate. I'm not immediately seeing the
> deadlock tonight, but then it's getting late...
>
> Is the application that's triggering this something you can share?
>
Sorry, I can't provide source code for these applications.
But drdbmake does what is described above: Preallocates a very big
chunk on disk and then
truncates it to its final length once it's done.
Please let me know if you need more details.
/Fredrik
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-10-27 8:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a125a870910180836i66781e1ey8113e7f8569f1fad@mail.gmail.com>
2009-10-18 15:47 ` Fwd: Ext4 bug with f Fredrik Andersson
2009-10-18 15:57 ` Fwd: Ext4 bug with fallocate Eric Sandeen
2009-10-19 9:49 ` Fredrik Andersson
2009-10-20 16:49 ` Fredrik Andersson
2009-10-21 0:24 ` Mingming
2009-10-22 7:37 ` Fredrik Andersson
2009-10-26 10:43 ` Fredrik Andersson
2009-10-21 2:20 ` Eric Sandeen
2009-10-21 9:08 ` Fredrik Andersson
2009-10-27 4:42 ` Eric Sandeen
2009-10-27 8:17 ` Fredrik Andersson [this message]
2009-10-27 13:56 ` Eric Sandeen
2009-10-27 15:29 ` Fredrik Andersson
2009-10-27 15:37 ` Eric Sandeen
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=a125a870910270117qa90debp8d5a9f90ffb8434@mail.gmail.com \
--to=nablaman@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).