As I understand the code mountall(8) did never spawn mount(8) because it did
not find the ID_FS_{TYPE,USAGE} attributes.
So mount only got called interactively by me, fetched the fs_vfstype from
fstab(5) and did what it was told to do, it called mount(2) which did not care
for the ext2 signature.
mount(8) does not search for fs signatures if the type is given.
Why can mountall not do the same?
If mountall would notice the ID_FS_AMBIVALENT attribute it could at least write
a warning message before spawning the recovery shell.
As I understand the code mountall(8) did never spawn mount(8) because it did
not find the ID_FS_{TYPE,USAGE} attributes.
So mount only got called interactively by me, fetched the fs_vfstype from
fstab(5) and did what it was told to do, it called mount(2) which did not care
for the ext2 signature.
mount(8) does not search for fs signatures if the type is given.
Why can mountall not do the same?
If mountall would notice the ID_FS_AMBIVALENT attribute it could at least write
a warning message before spawning the recovery shell.
According to /bugzilla. redhat. com/show_ bug.cgi? id=473514
https:/
cryptsetup and mkswap zap all existing filesystem signatures nowadays, but
existing filesystems could still have multiple signatures.