topic Re: error in vi editor in Operating System - HP-UX

error in vi editor

dhamodharan_1 — Tue, 21 Feb 2006 14:39:16 GMT

hi everyone

Iam getting the following error while creating a file in vi editor , can anyone help me to get resolve it"sample"
msgcnt 1052 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block ext
ent)
No space left on device [Warning - sample is incomplete]

Your edited changes will be lost if you do not complete a successful
write command before exiting. If you were writing out to your original
file, the previous contents of that file have been destroyed. Contact
your System Administrator BEFORE exiting if you need assistance.

[Hit return to continue]

I have given du and df both showing 0 blocks.

Thanks in advance
Dhamodharan.s

Re: error in vi editor

inventsekar_1 — Tue, 21 Feb 2006 14:42:46 GMT

can u show output of the command: bdf
u need to do something with the lvm..

Re: error in vi editor

Kent Ostby — Tue, 21 Feb 2006 14:43:05 GMT

Basically, your root file system is full.

Run the following command on the system:

find / -xdev -size +1000000c

This will show you the large files on your root file system.

Probably at least one of these doesn't belong.

If you post the output from the above command here, people will be able to add additional guidance.

Re: error in vi editor

Andy Torres — Tue, 21 Feb 2006 15:02:50 GMT

As well as the other suggestions, make sure /var is mounted. vi uses /var for temp space while editing a file.

Re: error in vi editor

Rodney Hills — Tue, 21 Feb 2006 15:03:00 GMT

If is possible /var/tmp is full too. /var/tmp is used as a temporary work area. (see "man ex" and "dir" option).

To override the workarea you could either place a value in .exrc or a one liner-
EXINIT "set dir=/tmp" vi /etc/fstab

HTH

-- Rod Hills

Re: error in vi editor

Mark Greene_1 — Tue, 21 Feb 2006 15:03:37 GMT

As stated the "/" file system is full. You may have a "core" file in "/". Or if /tmp or /home haven't been segregated into seperate file systems you may have a large file there.

mark

Re: error in vi editor

Sยภเl Kย๓คг — Tue, 21 Feb 2006 16:09:02 GMT

Hi

Use #bdf and identify the file system status. Cleanup / file system, as you have mentioned the error indicates, root file stem is full. And also you need have separate file systems for /home, /var, /usr ..

Regards,
Sunil

Re: error in vi editor

Indrajit_1 — Tue, 21 Feb 2006 19:07:57 GMT

Hi;

it seems ur root filesystem is full. u can try the following command

#dmesg (see the output)

#find / -size +1000000c -print

it will display the large file..

find out if can move some unwanted file to other location or can tar (tar -cvf file.tar file_name) files.

Cheers
indrajit

Re: error in vi editor

dhamodharan_1 — Tue, 21 Feb 2006 19:56:51 GMT

Hi

my BDF output is# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 204800 204800 0 100% /
/dev/vg00/lvol1 295024 29744 235776 11% /stand
/dev/vg00/lvol8 1560576 175600 1376528 11% /var
/dev/vg00/lvol7 2301952 1157024 1136000 50% /usr
/dev/vg00/lvol4 204800 162056 42440 79% /tmp
/dev/vg00/lvol6 1323008 1023520 297344 77% /opt
/dev/vg00/lvol5 20480 6272 14136 31% /home
#

DMESG output is

# dmesg

Feb 21 19:54
...
k extent)
msgcnt 973 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block exte
nt)
msgcnt 975 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block exte
nt)
msgcnt 977 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block exte
nt)
msgcnt 979 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block exte
nt)
msgcnt 981 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block exte
nt)
msgcnt 983 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block exte
nt)
msgcnt 985 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block exte
nt)
msgcnt 987 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block exte

Re: error in vi editor

James R. Ferguson — Tue, 21 Feb 2006 20:42:26 GMT

Hi:

You have your answer in that the "/" filesystem is full.

To see where the space is consumed, do:

# du -xk /|sort -k1nr|more

This sorts into descending order the largest-to-smallest usage.

It is very possible that a backup was run to a regular file instead of a special device file. Thus, look in '/dev' for non-special files. Typing '/dev/rmt/om' instead of '/dev/rmt/0m' is a common mistake and will usually fill the '/dev' directory in '/'.

The kernel reports the '/' mountpoint as '/dev/root'.

Regards!

...JRF...