From: Milan Broz <gmazyland@gmail.com>
To: Tim <tim-debian@sentinelchicken.org>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] System hang during mkfs
Date: Thu, 14 Nov 2013 22:56:45 +0100 [thread overview]
Message-ID: <5285471D.2070909@gmail.com> (raw)
In-Reply-To: <20131114212956.GN28665@sentinelchicken.org>
On 11/14/2013 10:29 PM, Tim wrote:
> Hello,
>
> I have run into a serious issue (system hang) while trying to create a
> luks-based loopback disk. I have reported this issue to Debian here:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729600
>
> That should have most of the technical details you need to start. I
> suspect the behavior I'm seeing is very similar to this:
> http://www.saout.de/pipermail/dm-crypt/2012-July/002544.html
>
> I am now running memtester on most of my VM's available memory and it
> is now on loop #3 with no issues identified.
>
> I'm really surprised to run across an issue like this under a stable
> kernel, so any advice you could give on how to further debug this
> would be greatly appreciated.
Well, the kernel Debian stable kernel, so it should be handled
really handled by the Debian distro bugzilla.
(Otherwise, please try more recent, ideally 3.12 stable kernel.
Using loop devices is quite common and I do not think there are recent
problems here.)
Also try use loop directly. Does mkfs works ok? What is the underlying
filesystem and mount parameters (on which image resides)?
If it "locks" paste kernel trace to bugzilla (through sysrq,
"echo t > /proc/sysrq-trigger" and see syslog.)
(It seems to me more like problem with loop device or combination
than with dmcrypt. Anyway, if you are able to reproduce it on upstream
kernel, add device mapper devel list to cc - dm-devel@redhat.com)
Milan
next prev parent reply other threads:[~2013-11-14 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 21:29 [dm-crypt] System hang during mkfs Tim
2013-11-14 21:56 ` Milan Broz [this message]
2013-11-14 23:07 ` Tim
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=5285471D.2070909@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=tim-debian@sentinelchicken.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.