why does a df on a wildcarded filesystem show multiple mounts to root
 

I have TSM running a 3 linux servers(running Redhat 4). each has /root on internal storage. each has filesystems named /opt/tivoli, /opt/tivoli_appdb, /opt/tivoli_log and /opt/tivoli_dbb.
I think this started happening recently, though cannot say what caused it. I use the DF -H /opt/t* to display all of my TSM related filesystems and the response I get back is causing me alarm: See below:

[root@ty-tsmprod01 ~]# df -h /opt/tivo*
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/TSMAPP_VG-tsm_lv
90G 12G 74G 14% /opt/tivoli
/dev/mapper/tsmdb_vg-tsm_db_lv
153G 109G 37G 75% /opt/tivoli_appdb
/dev/mapper/tsmprod01_vg-rootvol_lv
26G 13G 12G 51% //dev/mapper/tsmprod01_vg-rootvol_lv
26G 13G 12G 51% /
/dev/mapper/tsmdbb_vg-tsm_dbb_lv
258G 92G 154G 38% /opt/tivoli_dbb
/dev/mapper/tsmprod01_vg-rootvol_lv
26G 13G 12G 51% /
/dev/mapper/tivoli_vg-tivoli_log_lv
7.9G 6.1G 1.5G 82% /opt/tivoli_log
/dev/mapper/tsmprod01_vg-rootvol_lv
26G 13G 12G 51% /

Normally I would not see any of the multiple occurences of the rootvol_lv /. I should only see the display of /opt/t* filesystems.

Can someone explain why this might be happening or what I can look at to determine the cause? THanks

It's a little hard to tell from here, but my guess is that each of those is a directory matched by /opt/tivo* which is part of the root filesystem. When you run df with path arguments (and one usually doesn't, in my experience - usually it's just df to get a list of all filesystems), it gives you info for the filesystem on which each argument resides, and makes no attempt to eliminate redundancy. Try `df ~/*` for an example.

Regardless, nothing to be alarmed about. It's the right device file mounted to the right place; there's just redundant lines.