topic Re: Error: No space left on device in Operating System - HP-UX

Error: No space left on device

Simon Qu — Tue, 12 Oct 2004 17:24:50 GMT

Does anybody have experience on DG/UX?
This is a problem in DG/UX. When I try to mount a file system, I get "No space left on device" error. I am pretty sure there are space on the device.
This is not the place I should post this message. But, maybe I can get some ideas from here.

Thanks for any advice.

Re: Error: No space left on device

Steven E. Protter — Tue, 12 Oct 2004 18:53:06 GMT

On HP-UX it means you have a full filesystem.

bdf

find the full filesystem. Correct the problem.

Note that you can get this warning when a process tries to allocate space and the bdf might not show a full filesystem.

SEP

Re: Error: No space left on device

A. Clay Stephenson — Tue, 12 Oct 2004 18:56:31 GMT

It's been a very long time since I've worked on DG/UX but as I recall it's pretty standard UNIX. The first thing that I would do is make sure that there is free space in the filesystem that houses the mountpoint itself. Next, you probably need to do an fsck on the filesystem before trying to mount it. Finally, are you certain that you are using the mount command that is appropriate to the filesystem type?

Re: Error: No space left on device

Simon Qu — Wed, 13 Oct 2004 11:02:21 GMT

I have fsck error:
Fatal error: block 69443 is invalid inode table block.

Re: Error: No space left on device

Sanjay_6 — Wed, 13 Oct 2004 11:04:56 GMT

Hi,

seems like a corrupt filesystem.

Hope this helps.

Regds.

Re: Error: No space left on device

A. Clay Stephenson — Wed, 13 Oct 2004 11:12:57 GMT

That doesn't sound good at all but it may not be as bas as you think. Just as the mount comand must match the underlying filesystem type so must the fsck command. As I recall, DG/UX even supported the old s5 (System V) filesystem type as well as ufs so you need to run the appropriate fsck command.

Re: Error: No space left on device

Simon Qu — Wed, 13 Oct 2004 13:05:42 GMT

When I run fsck, I get:
block 69443 is invalid inode table block. Rewrite as empty block ?
If yes: fix this error, but any inodes that formerly occupied slots in this block will be cleared.
If no: ignore this error, but this file system is un-mountable.

Question:
If I choose YES to fix this error, do I have problem losing some data on that disk?

Thanks.

Re: Error: No space left on device

A. Clay Stephenson — Wed, 13 Oct 2004 13:34:49 GMT

The answer is probably. You might look at the man page for the mount command. Some UNIX flavors allow a -f (force) option to allow the mounting of a dirty filesystem - generally read-only.

Re: Error: No space left on device

Simon Qu — Fri, 15 Oct 2004 16:59:58 GMT

By using option -f, I was able to mount this file system. However, I have found it is an empty directory; there should be some files and sub-directories. How can I see these files and sub-directories in this file system?