vx_nospace -/dev/root file system full (1 block extent)

[Brendan Doherty]

By doing a restore, /dev/root/file system got full.
I am not even able to logon the console. I am receiving the following message :

vx_nospace -/dev/root file system full (1 block extent)
Can't rewrite terminal control enty for console

Can I restore (overwrite) /dev/root with omniback without bringing the system down. thanks

[Patrick Wallek]

Uhmmm....Why did you restore /dev/root???? Why is it mounted as /dev/root. That is an incorrect mount.

Your / filesystem should be mounted from /dev/vg00/lvol3.

How are you going to restore / if the filesystem is already full?

[Sachin Patel]

What kind of restore? fresotore, dump/restore, ignite?
I don't know what kind of file system is /dev/root
#ls -la /dev/root is block special file
brw-r----- 1 bin sys 255 0xffffff Aug 8 2001 /dev/root


Sachin

[pap]

I think you have booted the system in lvm maintenance mode and then you switched to multiuser mode. That's why you have /dev/root file system came in to picture.

Normally / should be in /dev/vg00/lvol3.

Now, you can do following.

boot you system in single user and then check the file system / .

check whether /dev/vg00/lvol3 is there in the system and where it is mounted.

If you have ignite backup then try to restore it and bring the system up.

[Sandip Ghosh]

I think instead of mount point you have restored on the / file system. Make sure before doing the restore mount all the required file system.

Sandip

[Michael Tully]

Hi,

I suggest you try to fix the mounting problem prior to attempting your restore.

# mv /etc/mnntab /etc/mnttab.save
# mount -a

Check to make sure that /dev/vg00/lvol3 is
set to be mounted on /

Michael

[Darrell Allen]

Is it possible you were restoring without some filesystem mounted? If so, you need to delete everything under that mount point. For example, let's say you restored /fs1 which is a mount point but unfortunately /fs1 wasn't mounted. You need to rm -r /fs1/* (and hidden files also) with /fs1 still unmounted.

Now the hard part - getting to where you can do that. If you can't login you may have to TOC the box and boot into a recovery shell from CD:

http://us-support.external.hp.com/cki/bin/doc.pl/sid=ec8319fb1af9c50da1/screen=ckiDisplayDocument?docId=200000047869323

http://us-support.external.hp.com/cki/bin/doc.pl/sid=3b52730a1cc59c788f/screen=ckiDisplayDocument?docId=200000047869320

Do you have an Ignite backup? Now may be the time to use it. If root can't log in, you're going to have to bring the system down (if it hasn't on it's own).

This is a good time to place a support call with HP.

Darrell