From: Peter Cordes <peter@cordes.ca>
To: "Dale R. Worley" <worley@alum.mit.edu>
Cc: Lucio Crusca <lucio@sulweb.org>, util-linux@vger.kernel.org
Subject: Re: [BUG] losetup: support for physical devices
Date: Mon, 26 Jan 2015 01:06:55 -0400 [thread overview]
Message-ID: <20150126050655.GG29504@cordes.ca> (raw)
In-Reply-To: <87mw56jkgq.fsf@hobgoblin.ariadne.com>
On Sun, Jan 25, 2015 at 10:21:09PM -0500, Dale R. Worley wrote:
> Lucio Crusca <lucio@sulweb.org> writes:
> > During a disaster recovery I found that losetup either
> >
> > 1. does not support creating loop devices that target physical devices. In
> > this case I think there exists a compelling reason to support them
> > (http://serverfault.com/questions/659484) and this bug report is a wishlist
> > bug
> >
> > or
> >
> > 2. it does support physical devices, but it is an undocumented feature (at
> > least in the manpage) and the warning it issues is misleading beacuse it
> > makes you think it doesn't support them ("losetup: /dev/sdc2: warning: file
> > smaller than 512 bytes, the loop device maybe be useless or invisible for
> > system tools"). In this case this could be a documentation bug.
> >
> > I haven't tested which of the two possibilities is the real situation, but
> > I'm pretty sure you already know.
>
> I don't recall what I've done that convinced me, but I'm *sure* that you
> can do
>
> losetup -o [offset] {-f[--show]|loopdev} /dev/sdXXX
Yup, it works for me. I posted an answer on
http://serverfault.com/questions/659484, gist of it is that
sudo losetup -o 32256 -f /dev/sdb3
sets up a loopback dev. Test with:
sudo tail -c 32257 /dev/sdb3 | sudo cmp - /dev/loop5
If you leave out -f or a specific arg like /dev/loop0, then the
command fails because losetup /dev/sdb3 means you're asking losetup
to print info on a loopback device called /dev/sdb3.
loop: can't get info on device /dev/sdb3: Inappropriate ioctl for device
IDK how you got it to print
losetup: /dev/sdc2: warning: file smaller than 512 bytes, the loop
device maybe be useless or invisible for system tools
--
#define X(x,y) x##y
Peter Cordes ; e-mail: X(peter@cor , des.ca)
"The gods confound the man who first found out how to distinguish the hours!
Confound him, too, who in this place set up a sundial, to cut and hack
my day so wretchedly into small pieces!" -- Plautus, 200 BC
prev parent reply other threads:[~2015-01-26 5:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 17:59 [BUG] losetup: support for physical devices Lucio Crusca
2015-01-14 20:08 ` Karel Zak
2015-01-14 20:13 ` Karel Zak
2015-01-26 3:21 ` Dale R. Worley
2015-01-26 5:06 ` Peter Cordes [this message]
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=20150126050655.GG29504@cordes.ca \
--to=peter@cordes.ca \
--cc=lucio@sulweb.org \
--cc=util-linux@vger.kernel.org \
--cc=worley@alum.mit.edu \
/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.