On 05/03/2017 10:13 AM, Peter Rajnoha wrote:
On 05/02/2017 03:32 PM, Jes Sorensen wrote:
On 04/28/2017 05:28 AM, Peter Rajnoha wrote:
On 04/28/2017 07:05 AM, NeilBrown wrote:
When an array is created the content is not initialized,
so it could have remnants of an old filesystem or md array
etc on it.
udev will see this and might try to activate it, which is almost
certainly not what is wanted.
So create a mechanism for mdadm to communicate with udev to tell
it that the device isn't ready. This mechanism is the existance
of a file /run/mdadm/created-mdXXX where mdXXX is the md device name.
When creating an array, mdadm will create the file.
A new udev rule file, 01-md-raid-creating.rules, will detect the
precense of thst file and set ENV{SYSTEMD_READY}="0".
This is fairly uniformly used to suppress actions based on the
contents of the device.
The scans in udev are primarily directed by blkid call which detects the
signatures and based on this information various other udev rules fire.
The blkid as well as wipefs uses common libblkid library to detect these
signatures - is mdadm going to use libblkid to wipe the signatures on MD
device initialization or is it relying on external tools to do this? How
is mdadm actually initializing/wiping the newly created MD device?
mdadm doesn't wipe data and it isn't supposed to. Being able to create
an array from drives with existing data is a feature.
It is the responsibility of the system administrator to handle drives
with existing data, in the same way the administrator is expected to
handle insertion of USB drives or external drives being powered on.
There's a difference though - when you're *creating* a completely new
device that is an abstraction over existing devices, you (most of the
time) expect that new device to be initialized. For those corner cases
where people do need to keep the old data, there can be an option to do
that. When you're inserting existing drives, you're not creating them -
when those device come from factory (they're "created"), they never
contain garbage and old data when you buy them.
Sorry, you are once again assuming *your* corner case to be the default
that everyone else expects. mdadm users (except for you and anaconda)
expect the current behavior.
Devices that come from the factory pretty much always contain old data,
plugin a USB drive and it will be filled with windows backup crap.
Jes
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
