From: Marvin Schmidt <marvin_schmidt@gmx.net>
To: linux-ide@vger.kernel.org
Subject: end_request: I/O error, dev hda, sector 0
Date: Fri, 17 Jul 2009 15:31:53 +0200 [thread overview]
Message-ID: <1247837513.12567.16.camel@pythagoras.homenetwork> (raw)
After updating from 2.6.30 to 2.6.31-rc1 i got a lot of
end_request: I/O error, dev hda, sector 0
messages when working on my dm-crypt'ed ext4 partition and I'm still
facing that issue with 2.6.31-rc3.
I'm able to reproduce it doing:
# cryptsetup luksOpen /dev/hda4 crypt-home
# mount /home
login as user
$ cp /path/to/some/file .
The relevant fstab-entry looks like:
/dev/mapper/crypt-home /home ext4 defaults,noauto 0 0
I bisected it to the following commit:
commit 647c7db14ef9cacc4ccb3683e206b61f0de6dc2b
Author: Mikulas Patocka <mpatocka@redhat.com>
Date: Mon Jun 22 10:12:23 2009 +0100
dm crypt: support flush
Flush support for dm-crypt target.
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Signed-off-by: Alasdair G Kergon <agk@redhat.com>
--
Do you need any more information/my config/etc.?
Best regards,
Marvin Schmidt
reply other threads:[~2009-07-17 13:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1247837513.12567.16.camel@pythagoras.homenetwork \
--to=marvin_schmidt@gmx.net \
--cc=linux-ide@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