linux-ext4 - Mkfs option to choose where metadata will be stored

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <4F44EBA0.5090606@robertoragusa.it>
Date:	Wed, 22 Feb 2012 14:20:32 +0100
From:	Roberto Ragusa <mail@...ertoragusa.it>
To:	linux-ext4@...r.kernel.org
Subject: Mkfs option to choose where metadata will be stored

Hi, [please CC me, I'm not subscribed]

is there any way to force allocation of metadata to a different device
or to a specific part (e.g. the begin) of the partition?

I see there is -O journal_dev to redirect the journal.
Can I do something different for metadata?

My idea is to have metadata on SSD and data on HDD.
With a linear RAID mapping, I would get a device which is a few GB of
SSD followed by a lot of HDD space.

Alternatively, I'm going to experiment with an approach where a volume group
is done on two PV: one HDD and one SSD. The idea is to create the LV on
the HDD and then move some extents (for example 0,1,64,65,128,129,...) to
the SSD, so that metadata happens to be on the SSD.
>From what I found about the on-disk format, this is highly approximate
and surely inelegant, so I wonder if a simpler solution exists.

Thanks.

-- 
   Roberto Ragusa    mail at robertoragusa.it
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html