Ignite Error: File Too Large

[Craig Roloff]

I ran make_sys_image & save_config on a B1000 running HP-UX11i and copied to results to my Ignite server (a C200 running HP-UX11.00). When I tried to push the image to another B1000 running HP-UX11.00, the log file showed the following error:

Could not mount VxFS "/dev/vg00/lvol3" at "/d_cfg_mnt_sb61/". File too large (errno -27)

The section in the save_config file for lvol3 shows:

logical_volume "lvol3" {
usage=VxFS
size=204800KB
blksize=1024
mount_point="/"
largefiles=FALSE
bad_block_relocate=false
contiguous_allocation=true
stripes=0
stripe_size=0KB
minor_number=0x03
disk[_hp_root_disk]
} # end logical_volume

Yes, I noted largefiles=FALSE but the volume size is only 200Mb.

Thanks!

[Michael Steele_2]

Hi Craig:

I've been searching around and, as you pointed out, all the hits point to largefiles.

Why don't you change to TRUE and retry.

I see that the entire volume size is only 200 MB, so there might be a ignire or pax or vxfs patching issue.

[Mridul Shrivastava]

UNIX errno values are associated with a symbolic name (like 5, EIO). The association between numeric value and symbol is defined in the include file /usr/include/sys/errno.h (see table below). The errno man page (which can be obtained with man 3 errno) provides an explanation for each errno symbol.
HP-UX error are usually caused by insufficient kernel parameters (and more seldom, index file corruption). If you encounter one of this ERRORs, you should get further information form the console or the syslog/other relevant logs.

HP-UX errno values Errno value Symbol Description
1
EPERM
Not super-user (root).

2
ENOENT
No such file or directory

3
ESRCH
No such process

4
EINTR
interrupted system call

5
EIO
I/O error

6
ENXIO
No such device or address

7
E2BIG
Arg list too long

8
ENOEXEC
Exec format error

9
EBADF
Bad file number

10
ECHILD
No children

11
EAGAIN
No more processes

12
ENOMEM
Not enough core

13
EACCES
Permission denied

14
EFAULT
Bad address

16
EBUSY
Mount device busy

17
EEXIST
File exists

18
EXDEV
Cross-device link

19
ENODEV
No such device

20
ENOTDIR
Not a directory

21
EISDIR
Is a directory

22
EINVAL
Invalid argument

23
ENFILE
File table overflow

24
EMFILE
Too many open files

25
ENOTTY
Not a typewriter

27
EFBIG
File too large

28
ENOSPC
No space left on device

29
ESPIPE
Illegal seek

30
EROFS
Read only file system

31
EMLINK
Too many links

32
EPIPE
Broken pipe

45
EDEADLK
A deadlock would occur

46
ENOLCK
System record lock table was full

47
EILSEQ
Illegal byte sequence

[john korterman]

Hi Craig,

you may also want to consult Doc ID: UIUXKBRC00009260 in the Tech base, although the error described there is not 100% like yours.

regards,
John K.

[V. Nyga]

Hi,

it seems like you have to increase the size of lvol3!

Instead of pushing the image to the new b-class you should boot from the ignite server (boot lan. install) to change the size of lvol3 - there it is possible.

HTH
Volkmar

[Craig Roloff]

I retried with largefiles=TRUE -- no change.

I was unable to locate Doc ID: UIUXKBRC00009260. Perhaps there was a typo? Is there an URL to this doc? Or better yet, an excerpt from the relevant portion?

As for increasing lvol3's size, the ignite process lets the user assign the LV sizes. I tried 2Gb without success.

Thanks again!

[V. Nyga]

Hi again,

how do you configure your filesystem?
Different lvol's for /var, /usr et cetera?
Can you try to assign 'all remaining' disk space to lvol3, so only one lvol for the whole '/'-dir?
Also define 'largefiles=true' in ignite.

How big is your hard disk?
How big is the image?
How big is the file system of the b-class where you created the image?

Volkmar

[john korterman]

Hi again craig,

no typo: UIUXKBRC00009260
But you need to have a valid support contract attached to your login in order for you to see it - quoting from it will violate Forum rules.
However, I think it is ok to just state that the document may not provide the ultimate answer, as the there described error message does not quite match the one you got.

regards,
John K.

[Craig Roloff]

It's a pretty standard layout, with lvols for /, /stand, /var, /usr, /tmp, /opt and /home. The image came from a B100 with a single 9Gb disk, of which about 7Gb is in use. The gzip'ed image is slightly less than 2Gb.

I'm trying to push it onto a B1000 with two 9Gb disks, so I've got lots of extra space. I suppose I could try disabling LVM.

Is there a way to increase the visibility of the problem? Some sort of "verbose on" switch so I can determine what the actual commands are that cause the error?

Thanks!

[V. Nyga]

Hi again,

try this link:
http://www12.itrc.hp.com/service/cki/docDisplay.do?docId=UIUXKBRC00009260&docLocale=en_US

They say it's a Ignite-UX version problem, so maybe another ignite version could help.

Hmmmm - you have a 11i client and a 11.00 server - this could cause a problem!
Can you use the b-class as server?

Volkmar

[V. Nyga]

and:
Can you give us the ignite versions you've installed?

V.

[V. Nyga]

one more doc 'How to add 11i client to 11.0 Ignite server':
http://www11.itrc.hp.com/service/cki/docDisplay.do?docLocale=en&docId=emr_na-c00934583-2

V.