tags 982459 +moreinfo user debian-rele...@lists.debian.org usertags -1 + bsp-2021-04-AT-Salzburg thank you
Hi, can you reproduce this bug on bullseye? (4.1-11) If so, what is your configuration (VM used, type of RAID)? Are all three conditions (/proc, /dev and /sys not mounted) required or does this also happen, if eg /dev and /sys are there but not /proc? If it still occurs until there would be a proper fix by upstream, a workaround like "are we in a chroot, if so, are the required things mounted, if not, fail", could be used to avoid the file system corruption. My own observations: Could not reproduce in virtualbox (both chroot and host system using recent bullseye), using RAID1, /dev/md0 on / type ext4 (rw,relatime,errors=remount-ro) # chroot chroot / # mdadm --examine --scan --config=partitions / # mdadm: cannot open /proc/partitions / # mdadm: No devices listed in partitions (in background on host running the mentioned find / command) No filesystem corruption after over 15 minutes, running the mdadm command in chroot several times didn't make a difference on that.
signature.asc
Description: This is a digitally signed message part.
