I have used a cpio script on SCO and older UNIX for a number of years. Recently I installed this same script on Linux to automate a daily backup to tape.
I am getting a message on all files backed-up "truncating inode number" I have searched everywhere I could think of for an explanation and cannot find any reference to this message. I think this has something to do with the -B or --block-size=nn option. I have tried various combinations but still get the message.
Anyone have an answer for me?

grabbed this from the net:
* From: ggw cds duke edu (Gregory G. Woodbury)
* To: redhat-list redhat com
* Subject: Re: cpio truncating inode number
* Date: Fri, 20 Nov 1998 15:06:52 -0500 (EST)

> I am using cpio to back up to a tape. On some files I get a message after
> the file name that says truncating inode number. The files seems to go the
> tape okay and I can read it back out and it seems okay. Can some one tell me
> what is going on? I hate errors I do not understand.

The cpio file format uses short ints for inode numbers, while the
ext2 uses int (generally 32-bits.) The truncation is a harmless artifact
of forcing ints into shorts. It is inconsequential on read-out because
the inode number in the cpio file is ignored.
--
sounds prettu harmless...


v.

HI Vince

Thanks for the explanation. At least now I know :-)

I did realise it was harmless, but I could not find a reasonable explanation and I am always fighting time so could not spend hours looking it up!!

THanks again

Eric