From: Marc Joliet <marcec@gmx.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: random i/o error without error in dmesg
Date: Sat, 07 May 2016 17:22:13 +0200 [thread overview]
Message-ID: <2609832.j3xfNZhHBD@thetick> (raw)
In-Reply-To: <1892242.Gv7fI7HlO2@thetick>
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
Am Saturday 07 May 2016
schrieb Marc Joliet <marcec@gmx.de>
>I'm thinking of filing
>a bug report with dovecot; perhaps none of their devs test with btrfs?
So I did this, and got a little bit of feedback. Quoting from the reply I
got:
"*.index.log files are always appended to using O_APPEND flag. Maybe this is
relevant.
Also when a new .log file is created it's opened without the O_APPEND flag and
the O_APPEND is added later. This was causing a bug recently in unionfs, which
ignored the flag change and caused log file corruption."
The other bit of advise was to stress test dovecot using imaptest, but I'll
have to do that when I have more time.
Greetings
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-05-07 15:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 11:23 random i/o error without error in dmesg Szalma László
2015-10-26 14:23 ` Marc Joliet
2015-10-27 6:23 ` Duncan
2015-10-27 9:19 ` Marc Joliet
2015-10-27 14:57 ` Szalma László
2015-10-27 20:54 ` Marc Joliet
2015-10-28 5:21 ` Duncan
2015-10-28 11:23 ` Austin S Hemmelgarn
2015-10-29 21:10 ` Marc Joliet
2015-10-30 9:32 ` Duncan
2015-10-28 8:44 ` Szalma László
2015-10-28 12:46 ` Duncan
2015-11-02 18:26 ` Szalma László
2016-02-21 12:01 ` Philipp Serr
2016-04-22 13:17 ` Marc Joliet
2016-05-07 15:22 ` Marc Joliet [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=2609832.j3xfNZhHBD@thetick \
--to=marcec@gmx.de \
--cc=linux-btrfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox