- Subject: Re: Bug#648367: device-mapper devices such as dm-crypt always have rotational=1; should inherit "rotational" setting from underlying devices
- From: Milan Broz <mbroz@xxxxxxxxxx>
- Date: Tue, 15 Nov 2011 18:05:31 +0100
- Cc: 648367@xxxxxxxxxxxxxxx, device-mapper development <dm-devel@xxxxxxxxxx>, Ben Hutchings <ben@xxxxxxxxxxxxxxx>
- In-reply-to: <20111115164151.GA24015@leaf>
- References: <20111110195943.12083.93273.reportbug@leaf> <1321232729.3059.42.camel@deadeye> <20111114022644.GB30421@leaf> <4EC215FA.1090303@redhat.com> <20111115164151.GA24015@leaf>
- Reply-to: device-mapper development <dm-devel@xxxxxxxxxx>
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20110807 Thunderbird/5.0
On 11/15/2011 05:41 PM, Josh Triplett wrote:
> I didn't know about that command; very nice, thanks! lsblk confirms
> that on my system, the physical disk has rotational=0 but the dm-crypt
> and LVM devices have rotational=1:
>
> NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED
> sda 0 512 0 512 512 0 cfq
> ├─sda1 0 512 0 512 512 0 cfq
> └─sda2 0 512 0 512 512 0 cfq
> └─sda2_crypt (dm-0) 0 512 0 512 512 1
> ├─leaf-swap (dm-1) 0 512 0 512 512 1
> └─leaf-root (dm-2) 0 512 0 512 512 1
>
> Does that help?
Thanks.
As noted on that bug earlier, it is already fixed in 3.2-rc1
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=4693c9668fdcec229825b3763876b4744f9e6d5e
(I thought it is fixed long time ago!)
There is no problem in DM layer with this (dmcrypt does not have own io scheduler)
but perhaps FS can use this flag for some optimization tuning, dunno.
Milan
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
[DM Crypt]
[Fedora Desktop]
[ATA RAID]
[Fedora Marketing]
[Fedora Packaging]
[Fedora SELinux]
[Yosemite Discussion]
[Yosemite Photos]
[KDE Users]
[Fedora Tools]
[Fedora Docs]