strange df -k output

[Michael Schulte zur Sur]

On one machine running 5.1A PK4 the df -k output is like this with too much space after the first column. Any idea, why?

ham10d /> df -k
Filesystem 1024-blocks Used Available Capacity
Mounted on
root_domain#root 393216 141570 238888 38%
/
/proc 0 0 0 100%
/proc
usr_domain#usr 6395904 1225028 5170876 20%
/usr
domain1#bda 17619408 29958 1154584 3%
/bda
domain1#dzde 17619408 3727745 1154584 77%
/dzde
domain1#eur 17619408 140764 1154584 11%
/eur
domain1#ov 17619408 468968 1154584 29%
/ov
domain1#pqpa 17619408 11328 1154584 1%
/pqpa
domain1#sybase 17619408 923244 1154584 45%
/sybase
domain1#tmp 17619408 172749 1154584 14%
/cluster/members/member0/tmp
domain1#transfer 17619408 29979 1154584 3%
/transfer
domain1#usys 17619408 520603 1154584 32%
/usys
domain1#uta 17619408 10336597 1154584 90%
/data
domain2#batch 8884584 2103182 6744488 24%
/batch
domain3#danzas3 14124816 57995 4712224 2%
/danzas3
domain3#dzn 14124816 21794 4712224 1%
/dzn
domain3#pro 14124816 9125656 4712224 66%
/pro
ham10d /> grep KIT /var/adm/patch/log/session.log
KITNAME> OSF520

[Ralf Puchner]

what do you mean? does the showfdmn differ from the df -k output?

[Michael Schulte zur Sur]

Hi Ralf,

I am talking not about spaces or asc(32) and not diskspace ;-).

Michael

[Ralf Puchner]

Michael,

I can not see a problem on the given output. Could you be more specific about the problem?
(maybe a sample)

[Michael Schulte zur Sur]

Hi Ralf,

you are right, this stupid programme cut out all the extra spaces. After the first column there are about 20 spaces, which makes the output go into the next line and not very readable. When I tried to find out, whether a single mount point caused the problem I found a strange line, which is not shown with df -k. It is the automount daemon. Do you think, this would influence the output of df even though it does not show up in the listing?

regards

Michael

ham10d.hamed.de.danzas.com:(pid660) 0 0 0 100%
/net

[Hein van den Heuvel]

Michael,

Your explanation did not help me understand the problem any better.

Yeah, this forum softwate mangles spaces. Very annoying. I've exchanged mail with Dan.

Anyway, to make progress on you prioblem:
- Please attach the output with problem as a text file.
- Please identify which line(s) we shoudl look at more
- Please tell us whether this problem happens to be observerd under Pk4 or whether this used to work differently before and going to pk4 made a change.

[Michael Schulte zur Sur]

Hi Hein,

thanks for the idea. I wonder, why I didn´t come up with it myself. Anyway, I updated from 4.0F and this problem seems to be only on this machine.

Micha

[Mohamed K Ahmed]

I still can't see a problem with the spaces after the mounted device, maybe you have different settings on the emulator you are using, or may be the terminal you are using is wrapping the output.
Any way, this is not a problem to me and it should not cause any problems to you

Regards
Mohamed

[Ralf Puchner]

I can also not see a problem on the given output (attached file). Have you checked the output file on a normal PC/machine prior?

[Michael Schulte zur Sur]

Ther are way too many spaces after the fileset name(first column). Usually all fit´s on one line.

Micha

[Joris Denayer]

Michael,

There have been changes in the format of some fields.
You say that this happens on one system only.
Can you post the output of
# what /bin/df
of a system with good output and of one with bad output.

Joris

[Michael Schulte zur Sur]

Hi Joris,

attached the output. It seems to be the same. Usually the position of columns only change due to the length. I still wonder, whether the automountis the reason, even if does not show up on df.

Michael

[Joris Denayer]

Michael,

1) These df's are indeed the latest version for v5.1A


2) I just discovered a similar problem on a system with V4.0G.
On the system with automount configured, a lot of spaces are added.
On the system without automount, the length of the first field is calculated correctly.

So, in my humble opinion, this has nothing to do with v5.1a PK4 in particular.


But, this will not help.

Joris

[Michael Schulte zur Sur]

Hi Joris,

thanks for the information. So my situation does not seem to special. So I will have to wait and see, if HP is going to correct it one day.

thanks for all participation,

Michael

[Ralf Puchner]

Or you open a call within the support center if you have a valid support contract.