From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 118041] My tricky script involving zram and device mapper hangs on "mount"
Date: Tue, 17 May 2016 16:48:43 +0000 [thread overview]
Message-ID: <bug-118041-13602-BW2VrKYgyo@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-118041-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=118041
--- Comment #2 from _Vi <vi0oss@gmail.com> ---
cryptie4-ff: 0 3072000 linear 251:0 672802816
Maybe I'll try to make special stand-alone script for demonstrating the
problem.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2016-05-17 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 21:22 [Bug 118041] New: My tricky script involving zram and device mapper hangs on "mount" bugzilla-daemon
2016-05-17 16:27 ` [Bug 118041] " bugzilla-daemon
2016-05-17 16:48 ` bugzilla-daemon [this message]
2016-05-17 17:55 ` bugzilla-daemon
2016-05-17 18:59 ` bugzilla-daemon
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=bug-118041-13602-BW2VrKYgyo@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).