Sponsored Content
Full Discussion: file sysstem size problem
Top Forums UNIX for Dummies Questions & Answers file sysstem size problem Post 10543 by Prafulla on Friday 16th of November 2001 02:36:04 AM
Old 11-16-2001
CPU & Memory

Hi.....

How to recover a corrupted or damaged LIF area.....
because when i am traying to boot in single user mode by interupting the booting process and invoking ISL ,it is giving LIF magic error as i have mentioned earlier..

please suggest any way to restore LIF area.

thanks and regards
PrafulSmilie
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Hp Unix file size problem

We have two files /var/adm/wtmp and /var/opt/OV/tmp/OpC/guiagtdf Could you please tell me if what these files are and if I can purge them as they are very big and Vi will not let me look at them, it gives me a message 'file to long'. Help any ideas Thanks :cool: (3 Replies)
Discussion started by: A Roberts
3 Replies

2. Shell Programming and Scripting

ftp UnixWare File Size Problem

Hi Engg. ! :cool: When I am trafering a file through ftp from windows to UNIX having size about 1.24 GB then at the end of file transfer I got a error message "Extended file size limit (coredump)" and finnally ftp stop, whenever on other UNIX server the same file from windows... (1 Reply)
Discussion started by: Niraj Gopal Sha
1 Replies

3. Filesystems, Disks and Memory

file size problem using Apache 1.3.12 on Solris 8

I am running into a problem after uploading files to a document archive on our local intranet. If the file size is >1 MB, then whenever I get a "list of contents" of the directory, the browser returns ""page cannot be displayed. This seems to happen if any file in the directory is >1MB. Every... (1 Reply)
Discussion started by: Gibby9
1 Replies

4. Solaris

command to find out total size of a specific file size (spread over the server)

hi all, in my server there are some specific application files which are spread through out the server... these are spread in folders..sub-folders..chid folders... please help me, how can i find the total size of these specific files in the server... (3 Replies)
Discussion started by: abhinov
3 Replies

5. SCO

File size problem

I'm working on a IBM PC Serveur 325. I have a sequential file with more than 800000 records. The size of that file is 136755200. I wrote a cobol program (RM cobol) to delete records. Now the file has 180000 records and the size still the same 136755200. What I need to do to decrease the size.... (1 Reply)
Discussion started by: royinfo
1 Replies

6. UNIX for Dummies Questions & Answers

File size problem

I'm working on a IBM PC Serveur 325. I have a sequential file with more than 800000 records. The size of that file is 136755200. I wrote a cobol program (RM cobol) to delete records. Now the file has 180000 records and the size still the same 136755200. What I need to do to decrease the size.... (3 Replies)
Discussion started by: royinfo
3 Replies

7. Shell Programming and Scripting

The scripts not able to make the file to size 0, every times it go back to its original size

#!/bin/sh ########################################################################################################## #This script is being used for AOK application for cleaning up the .out files and zip it under logs directory. # IBM # Created #For pdocap201/pdoca202 .out files for AOK #1.... (0 Replies)
Discussion started by: mridul10_crj
0 Replies

8. Shell Programming and Scripting

file size problem

Hi everyone can you people please help me in the problem below -bash-3.00$ ls -ltr abc abc.tar -rw-r--r-- 1 1hinaa2 17 Jan 17 14:09 abc -rw-r--r-- 1 1hinaa2 2048 Feb 17 07:03 abc.tar -rw-r--r-- 1 1hinaa2 135 Feb 17 07:03 abc.tar.gz why this strange... (2 Replies)
Discussion started by: aishsimplesweet
2 Replies

9. Shell Programming and Scripting

file size problem

Hi Everyone I am having very strange problem I want to know if i do ls -ltr then the file size it return will always be in bytes or it could be different in different scenario. or is there any command which will return the size of file in only one unit. Please help... (8 Replies)
Discussion started by: aishsimplesweet
8 Replies

10. UNIX for Dummies Questions & Answers

Ls directory size reporting byte size instead of file count

I have been searching both on Unix.com and Google and have not been able to find the answer to my question. I think it is partly because I can't come up with the right search terms. Recently, my virtual server switched storage devices and I think the problem may be related to that change.... (2 Replies)
Discussion started by: jmgibby
2 Replies
lif(4)							     Kernel Interfaces Manual							    lif(4)

NAME
lif - logical interchange format description DESCRIPTION
LIF (Logical Interchange Format) is a Hewlett-Packard standard mass-storage format that can be used for interchange of files among various HP computer systems. A LIF volume contains a header (identifying it as a LIF volume) and a directory that defines the contents (i.e. files) of the volume. The size of the directory is fixed when the volume is initialized (see lifinit(1)) and sets an upper bound on the number of files that can be created on the volume. HP-UX contains a set of utilities (referred to as lif*(1)) that can be used to: o Initialize a LIF volume (i.e. create a header and an empty directory), o Copy files to and from LIF volumes, o List the contents of LIF volumes, o Remove LIF files, o Rename LIF files. The lif*(1) utilities are the only utilities within HP-UX where the internal structure of a LIF volume is known. To the rest of HP-UX, a LIF volume is simply a file containing some unspecified data. The term LIF volume should in no way be confused with the HP-UX notion of a file system volume or mountable volume. LIF utilities on HP-UX currently support three file types, ASCII (1), BINARY (-2) and BIN (-23951). Three copying modes are associated with these file types: If the copying mode is ASCII and an HP-UX file is being copied to a LIF volume, the utility strips the trailing LF (line-feed) character, and inserts two bytes of record length in front of each record. These records are then written to a LIF-formatted medium. When copying a LIF ASCII file to HP-UX the two-byte record length is stripped and a trailing LF is appended. These records are then written to the destination. In this mode of copying, the length of the file is preserved. The default file type for this mode of copying is ASCII (1). If the copying mode is and an HP-UX file is being copied to a LIF volume, the utility simply inserts two bytes for record length in front of each 1-Kbyte record. A trailing fractional block has a count reflecting the number of bytes in that block. No interpretation is placed on the content of the records. These records are then written to a LIF-format medium. When copying a LIF file to an HP-UX file in copying mode, the record lengths are stripped and the content of records is directly written to the destination. In this mode of copying, the length of the binary file is preserved. The default file type for this mode of copying is (-2). If the copying mode is RAW, and an HP-UX file is being copied to a LIF volume, the utility simply copies the raw data to the destination. File sizes that are not integer multiples of 256 bytes are padded with nulls to the next higher multiple. Therefore, When copying a LIF file to an HP-UX file in RAW mode, the information is copied directly without any interpretation placed on the content of the source. The default file type for this mode of copying is (-23951). A LIF volume can be created on any HP-UX file (either regular disk file or device special file) that supports random access via (see lseek(2)). lif*(1) utilities. See lifinit(1) for details. Within a LIF volume, individual files are identified by 1- to 10-character file names. File names can consist of uppercase alphanumeric characters (A through Z, 0 through 9) and the underscore character (_). The first character of a LIF file name must be a letter (A through Z). The lif*(1) utilities accept any file name (including illegal file names generated on other systems), but can only create legal names. This means that files whose names contain lowercase letters can be read but not created. LIF file names are specified to the lif*(1) utilities by concatenating the HP-UX path name for the LIF volume followed by the LIF file name, separating the two with a colon For example: specifies LIF file accessed via HP-UX device special file specifies LIF file within HP-UX disk file Note that this file-naming convention is applicable only for use as arguments to the lif*(1) utilities, and does not constitute valid path naming for any other use within the HP-UX operating system. lif*(1) utilities. SEE ALSO
lifcp(1), lifinit(1), lifls(1), lifrename(1), lifrm(1). lif(4)
All times are GMT -4. The time now is 06:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy