From: Karel Zak <kzak@redhat.com>
To: Francis Moreau <francis.moro@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: losetup: failed to setup loop device > 1
Date: Tue, 7 Oct 2014 11:17:11 +0200 [thread overview]
Message-ID: <20141007091711.GB8057@x2.net.home> (raw)
In-Reply-To: <54330294.1090908@gmail.com>
On Mon, Oct 06, 2014 at 10:59:00PM +0200, Francis Moreau wrote:
> On 10/06/2014 07:40 PM, Karel Zak wrote:
> > On Mon, Oct 06, 2014 at 06:35:20PM +0200, Francis Moreau wrote:
> >> One last details is that the system uses pretty old stuff: kernel
> >> 3.4.50, util-linux 2.21.1.
> >
> > $ git log --oneline v2.21.. -- lib/loopdev.c sys-utils/losetup.c | wc -l
> > 62
> >
> >> Could anybody give me some help ?
> >
> > update, this is upstream mailing list I have doubts anyone is ready
> > to help you with code released 2 years ago.
>
> well it looks like more a kernel issue since the sequence of syscalls
> done by losetup looks correct. Maybe someone here already encountered
> this...
>
> I just found that loop module was loaded with max_part=16 and
> CONFIG_BLK_DEV_LOOP_MIN_COUNT=8. If max_part is set to 0 then the issue
> is gone :-/
Well, if you have kernel that provides /dev/loop-control then you
don't have to set CONFIG_BLK_DEV_LOOP_MIN_COUNT at all. I guess
"8" (kernel upstream default?) is mostly about backward compatibility.
For example fedora uses CONFIG_BLK_DEV_LOOP_MIN_COUNT=0. All is
dynamically allocated by kernel + udev.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2014-10-07 9:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 16:35 losetup: failed to setup loop device > 1 Francis Moreau
2014-10-06 17:40 ` Karel Zak
2014-10-06 20:59 ` Francis Moreau
2014-10-07 9:17 ` Karel Zak [this message]
2014-10-07 9:32 ` Francis Moreau
2014-10-08 8:57 ` Francis Moreau
2014-10-08 9:44 ` Karel Zak
2014-10-08 10:05 ` Francis Moreau
2014-10-08 10:58 ` Francis Moreau
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=20141007091711.GB8057@x2.net.home \
--to=kzak@redhat.com \
--cc=francis.moro@gmail.com \
--cc=util-linux@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).