From: Jeff Moyer <jmoyer@redhat.com>
To: Christophe Saout <christophe@saout.de>,
device-mapper development <dm-devel@redhat.com>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: [dm-devel] Block regression since 3.1-rc3
Date: Mon, 03 Oct 2011 10:43:52 -0400 [thread overview]
Message-ID: <x49pqieyw2f.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <1317397918.27140.15.camel@localhost> (Christophe Saout's message of "Fri, 30 Sep 2011 17:51:57 +0200")
Christophe Saout <christophe@saout.de> writes:
> I think you guys should know - maybe you have an idea or have something
> for me to test. I would have tried to file a bug somewhere, but half of
> the infrastructure is down at the moment.
You didn't include the top few lines which tell us what went wrong. I
tried to reproduce this myself, but I ran into other issues with GFS2.
Anyway, it would help a great deal if you could retrigger the failure
and provide the full failure output. You can get that by issuing the
'dmesg' command and redirecting it to a file. And please CC me on any
future correspondences on this issue.
Thanks!
Jeff
next prev parent reply other threads:[~2011-10-03 14:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 15:51 Christophe Saout
2011-09-30 18:02 ` [dm-devel] " Christophe Saout
2011-10-03 14:43 ` Jeff Moyer [this message]
2011-10-04 12:02 ` Christophe Saout
2011-10-04 13:32 ` Jeff Moyer
2011-10-04 15:06 ` Christophe Saout
2011-10-06 19:51 ` Jeff Moyer
2011-10-06 22:02 ` Christophe Saout
2011-10-08 11:02 ` Shaohua Li
2011-10-08 12:05 ` Christophe Saout
2011-10-09 4:26 ` Shaohua Li
2011-11-01 4:54 ` illdred
2011-10-08 16:14 ` Mike Snitzer
2011-10-09 4:31 ` Shaohua Li
2011-10-09 7:16 ` Shaohua Li
2011-10-09 8:12 ` Christophe Saout
2011-10-09 13:47 ` Christophe Saout
2011-10-10 21:33 ` Tejun Heo
2011-10-11 19:56 ` Mike Snitzer
2011-10-11 20:52 ` Tejun Heo
2011-10-11 22:07 ` Jeff Moyer
2011-10-09 8:08 ` [dm-devel] " Shaohua Li
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=x49pqieyw2f.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=axboe@kernel.dk \
--cc=christophe@saout.de \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®