Comment 8 for bug 839118

Looking at the other bugs on mountall, I think this is the same as bug #730023 - I see that you have another partition configured with "none" as the mount target. So it's probably the ordering of these two filesystems in the fstab that has the effect.

Why do you have a filesystem listed with a mount point of "none"? It's a bug in mountall that this fails to work, but that seems like cruft that shouldn't be there.