Hi Tomas, On Fri, Jan 3, 2025 at 3:54 AM Tomas Mudrunka <tomas.mudrunka@xxxxxxxxx> wrote: > > > The problem is that system service will recognize raid disks and > > assemble the array automatically, you might what to disable them. > > Actualy user is forced to work with MD device from the get go. > This is how you would typicaly use mdadm to write metadata to disk: > > $ truncate -s 1G test.img > $ mdadm --create /dev/md0 --level=1 --bitmap=internal --raid-devices=2 test.img missing > mdadm: must be super-user to perform this action > mdadm: test.img is not a block device. > > Following is unfit for my usecase: > * It requires me to reference /dev/md0 (i don't want to involve kernel at all) > * It requires super-user (no need, i just want to write bytes to my own file) > * Refuses to work on regular file (once i run it as super-user) I think I understand the use case now. One question though: Do we really need to write the bitmap data at "mdadm --create" time? Can we instead wait until the array is assembled by the kernel? Thanks, Song [...]
