Added the possibility to extend the number of slots for NFS and

Added the possibility to extend the number of slots for NFS and
CIFS mount points on the fly.

Mail from Ivana Varekova (varekova@redhat.com) 02/02/2011:
Hello, I'm sending 6 patches - 3 for nfsiostat and 3 for cifsiostat
nfsiostat:
    nfsiostat.patch - adds the possibility to extend the number of
slots for nfs mount points during the nfsiostat run

cifsiostat:
    cifsiostat.patch - adds the possibility to extend the number of
slots for cifs mount points during the cifsiostat run

See also mail from Masanari Iida (masanari.iida@hp.com) 28/01/2011:
Hello

I have a feedback about nfsiostat behavior.

Description
nfsiostat need to be run _AFTER_ the NFS share is mounted.

Version.
nfsiostat in sysstat 9.1.7

How to reproduce
(1) Run nfsiostat -k 1
(2) Mount one NFS share
(3) Check nfsiostat output.

Expected result.
nfsiostat start to report the NFS share's activities, after I mount it.

Actual result.
nfsiostat not reporting the mounted NFS share, even after it is mounted.

Additional information:
If I mount the NFS share _BEFORE_ i run nfsiostat, nfsiostat reports the
NFS share's information.  And also, if I umount the NFS share,
the line disappeared. (This is expected.)

It is because, the environment is using autofs,  mount and umount often
happens on the system.
But I continously running the iostat -kn  to collect the statics, then I have
encounteded this symptom.  (And tested with nfsiostat )

In case of multiple NFS mount points, the symptom is bit different.
If an additional NFS share is mounted BEFORE this test is done,
the target NFS share appeared after mount it.  And dissapeared it after umount.
But if I do the same thing one more time, it is not display any more.

========

To say the truth,  the original symptom is happen on sysstat 7.0
on RHEL5 system, using iostat -kn. The environment uses autofs.
I wanted to confirm if the upstream version already fixed this symptom,
so that's why I downloaded the latest tar ball and tried.
But so far, the similar symptom still exist.

If you think this is current known limitation or known bug,
please document it in man page or FAQ page of your web.

Regards,

Masanari Iida