Util-Linux package development
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>,
	Kay Sievers <kay.sievers@vrfy.org>
Cc: util-linux <util-linux@vger.kernel.org>
Subject: Re: Buffer I/O error, with latest losetup on first run
Date: Wed, 18 Jan 2012 13:13:01 +0100	[thread overview]
Message-ID: <20120118121301.GA2371@x2.net.home> (raw)
In-Reply-To: <4F16279F.3040100@yahoo.com.ar>

On Tue, Jan 17, 2012 at 10:59:59PM -0300, Gerardo Exequiel Pozzi wrote:
> Using (losetup from util-linux 2.20.620-4360-dirty) and Linux-3.2.1.
> 
> Using losetup as first time, if loop module is not loaded, losetup -f
> file-equal-or-below-1MiB I get: "Buffer I/O error on device loop0, logical
> block 0" (sometimes get one message, or two or three, ...)

It does not sound like userspace problem, I guess that the message comes
from kernel (dmesg). It would be also nice to have strace output.

> 
> Can be reproducible again if loop module is unloaded then execute losetup.
> Does not happen if module is loaded previously to losetup.
> Happens independently if /dev/loop0 exists or not.
> 
> Does not happen with losetup from 2.20 under the same conditions.

The new losetup uses /dev/loop-control to get the new free loop device.

Kay, any idea?

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  reply	other threads:[~2012-01-18 12:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-18  1:59 Buffer I/O error, with latest losetup on first run Gerardo Exequiel Pozzi
2012-01-18 12:13 ` Karel Zak [this message]
2012-01-18 12:51   ` Kay Sievers
2012-01-18 15:33   ` Gerardo Exequiel Pozzi

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=20120118121301.GA2371@x2.net.home \
    --to=kzak@redhat.com \
    --cc=kay.sievers@vrfy.org \
    --cc=util-linux@vger.kernel.org \
    --cc=vmlinuz386@yahoo.com.ar \
    /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