I'd like to make another guess at what the problem is. Instead of using
cp, try the operation using cpio. The difference is that cpio (under
Linux) knows how to copy using 32-bit inodes. It's not clear that cp knows
how to link files whose inodes are larger than a 16-bit offset.
I could be wrong.
Oh. yeah. One other thing. Run fsck and delete everything before
restarting.
--
----------Time flies like the wind. Fruit flies like a banana.----------------
--------Stranger things have happened but none stranger than this.-------------
Steven W. Orr [EMAIL PROTECTED] <site of former bang addr:-)>
---------------"Listen to me! We are all individuals."-------------------------
On Wed, 24 Nov 1999, Brian wrote:
=>check your termination and term pwr on the drive that is messing up.
=>
=>On Wed, 24 Nov 1999, Eric Wood wrote:
=>
=>> I partioned my second 9 gig SCSI drive to have one filesystem:
=>>
=>> # mke2fs /dev/sdb1
=>> # mount /dev/sdb1 /vol1
=>> # cp -R /usr /vol1
=>>
=>> After a while of copying I get many of these messages:
=>>
=>> EXT2-fs error(device sd(8,17)): ext2_add_entry: bad entry in directory
=>> #34490: inode out of bounds -offest=0, inode=2097025, rec_len=12, name_len=1
=>>
=>> and
=>>
=>> EXT2-fs error(device sd(8,17)): ext2_readdir: bad entry in directory #
=>> 34490: directory entry across blocks - offset=0, inode=1852793705,
=>> rec_len=25956, name_len=110
=>>
=>>
=>> If the /dev/sda1 filesytem can handle all the /usr files, why can't
=>> /dev/sdb1?
=>> -Eric Wood
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
