mount weirdness
I recently rebooted after an upgrade that generated
"Jul 28 17:13 initrd.img-4.19.0-5-686-pae"
and when I was finally U&R I discovered that a mount didn't
happen. (I am on Debian 10 Bullseye and my last kernel
resulted in "Jul 18 17:23 vmlinuz-4.19.0-5-686-pae".)
I have mount points /wa1-/wa4 and I have been using them
literally for years with no problem.
So anyway, I typed in "sudo mount /dev/sdb2 /wa1" and it
seemed to finish successfully, but "ls /wa1" indicated that
in fact it had not. Nothing mounted on wa1! Many other tests
told me the same thing. "umount /wa1" said "not mounted"!
After trying many things I discovered that 1) I can mount
/dev/sdb2 on any mount point except /wa1 and 2) I can't
mount any /dev/sdxx on /wa1!! So I mounted sdb2 on /wa11,
"rmdir /wa1"and "ln -s /wa11 /wa1" and everything seems to
work OK.
It seems that something in the mount process does not like
"wa1" for a mount point. Anybody have similar recent problems?
Reply to: