Hello all, I need help trying to debug a weird bug that I'm hitting. I've got a server with fairly large storage (>100TB) that needs to handle very-small-files. Due to performance considerations I decided to split the large array into 128 ext4 partitions (rather than use a single xfs partition).
I recently upgraded the server to F24 (w/ kernel 4.5.5, 4.6.4 refuses to boot on the machine) and I'm now facing a weird problem: On boot, systemd fails to mount all the partition dropping to emergency shell. At least as far as I can see, udev fails to create some symbolic links under /dev/<LVMVGName>, even though it has no issues creating the same symbolic links under /dev/mapper/<LVMVGName>-<LVMLGName>_PXX. On the other hand systemd still uses the broken /dev/<LVMVGName> device units, even though we moved all the entries in fstab to /dev/mapper/<LVMVGName>-<LVMLGName>_PXX and manually ran systemd-fstab-generator. Valid mapper: $ ls -l /dev/mapper/VolRoot-LogStorageMData_P* | wc -l 128 Invalid VGName: $ ls -l /dev/VolRoot/LogStorageMData_P* | wc -l 95 <--- Should be 128. fstab: $ cat /etc/fstab | grep VolRoot-LogStorageMData_P | wc -l 128 systemd broken unit files: $ systemctl -a --no-pager | /bin/grep dev-VolRoot-LogStorageMData | wc -l 95 <--- Should be 128. Any suggestions are welcome. - Gilboa -- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
