>>> I see where the root fs option is passed to the kernel in the boot >>> script, but it surprises me that neither mount nor df show / in their >>> listings. Although findmnt does show / in it's listing. Is this by >>> design? If so, I'll make a note in the wiki. >> The root file system in the output of df in shown in /dev/root mounted on / >> > Indeed, that is what I expect to see. But when I run df no entries for > /dev/root on / are shown. > > This is all I get: > > # df -h > > Filesystem Size Used Avail Use% Mounted on > /run 187M 1.1M 186M 1% /var/run > > No /boot, no /, just /run. > I believe I have figured this out. /etc/mtab should be a symbolic link to /proc/self/mounts (at least systemd docs say so), but it was a static text file. At boot time, it would have entries for mqueue, debugfs, configfs and sometimes (not always) /run and /run/lock written to it (I don't know what is doing the writing). However the rest of the mount tree would be invisible to df and mount (they must only source /etc/mtab). Thus giving me the strange behavior. Also, as no process would clear /etc/mtab at shutdown, it would grow with multiple redundant entries. Creating the symlink: /etc/mtab -> /proc/self/mounts, fixed these two problems. df & mount now report on the full filesystem tree, and mtab stays the same size across reboots.
This would seem to be a problem with the filesystem layout for the RPi image, but I'm afraid I don't know how to fix that. -Alex -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
