From: Milan Broz <mbroz@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: 648367@bugs.debian.org, Ben Hutchings <ben@decadent.org.uk>,
Josh Triplett <josh@joshtriplett.org>
Subject: Re: Bug#648367: device-mapper devices such as dm-crypt always have rotational=1; should inherit "rotational" setting from underlying devices
Date: Tue, 15 Nov 2011 08:34:18 +0100 [thread overview]
Message-ID: <4EC215FA.1090303@redhat.com> (raw)
In-Reply-To: <20111114022644.GB30421@leaf>
On 11/14/2011 03:26 AM, Josh Triplett wrote:
> OK, I suppose I don't actually care what rotational shows for a
> device-mapper device backed by rotating media. The case I care about:
> when the underlying media has rotational=0, the dm device definitely
> shouldn't have rotational=1.
Rotational flag is inherited in DM core, nothing dm-crypt specific.
And it works (for several kernel releases already):
create test scsi disk (also with discards)
# modprobe scsi_debug dev_size_mb=16 sector_size=512 num_tgts=1 lbpu=1
# grep scsi_debug /sys/block/*/device/model
/sys/block/sdj/device/model:scsi_debug
Map some crypt device over it
# echo "password" | cryptsetup create sdj_crypt /dev/sdj
And now see inherited ROTA flag (it is /sys rotational)
# lsblk -t /dev/sdj
NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED RQ-SIZE
sdj 0 512 32768 512 512 0 cfq 128
`-sdj_crypt (dm-0) 0 512 32768 512 512 0 128
Please paste lsblk -t output tree if you think there is a bug, do not blindly
check all dm-X devices queues.
Milan
next prev parent reply other threads:[~2011-11-15 7:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111110195943.12083.93273.reportbug@leaf>
2011-11-14 1:05 ` Bug#648367: device-mapper devices such as dm-crypt always have rotational=1; should inherit "rotational" setting from underlying devices Ben Hutchings
2011-11-14 2:26 ` Josh Triplett
2011-11-15 7:34 ` Milan Broz [this message]
2011-11-15 16:41 ` Bug#648367: [dm-devel] " Josh Triplett
2011-11-15 17:05 ` Milan Broz
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=4EC215FA.1090303@redhat.com \
--to=mbroz@redhat.com \
--cc=648367@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=dm-devel@redhat.com \
--cc=josh@joshtriplett.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.