Package: dracut-install Followup-For: Bug #1079443 X-Debbugs-Cc: tj.iam...@proton.me Control: affects -1 + debvm
Results of further diagnosis. First, discovered that -v overrides --debug: removing -v from the command line allowed debug messages and removing -o means any missing modules causes an error, so now the small reproducer reports: dracut-install: Handle module '=drivers/block' dracut-install: Handling =drivers/block dracut-install: Ignoring /lib/modules/6.10.6-armmp/extra/drivers/block dracut-install: Ignoring /lib/modules/6.10.6-armmp/kernel/drivers/block dracut-install: Ignoring /lib/modules/6.10.6-armmp/kernel/drivers/block dracut-install: Ignoring /lib/modules/6.10.6-armmp/updates/drivers/block dracut-install: ERROR: installing '=drivers/block' The "Ignoring" message is generated in install_modules() when an FTSENT is not a file nor a symbolic link. There are 13 files and sub-directories in the directory but we only see 2 messages for the module's path. Since the directory is visited twice by the fts* functions, once for preorder and again for postorder, that suggests something interesting is going on. I note fts_open( ... FTS_NOSTAT ...) and confirm with strace that no stat*() functions are called on the contents of the directory. This would imply that the FTSENT fts_info == FTS_NSOK and that would explain the results being seen.
