I wasn't able to reproduce this on a small loopback fs. Just to see
what would happen, I let e2fsck clear:
$ e2fsck -vfy /dev/sda9
e2fsck 1.34 (25-Jul-2003)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Symlink /usr/lib/gcc-lib/powerpc-unknown-linux-gnu/3.2.3/libgcc_s.so
(inode #31561) is invalid.
Clear? yes
Illegal block number passed to ext2fs_unmark_block_bitmap #1734502764
for in-use block map
Illegal block number passed to ext2fs_unmark_block_bitmap #1734502764
for block bitmap for /dev/sda9
pid 10: killed by signal 11
So I guess I have some fs corruption going on. I'll see if I can find a
good way to reproduce this, and report back if I can. I'm guessing it
probably has to do with ppc being in poorer shape than x86 in 2.6. :\
On Thu, 2003-08-28 at 07:11, Andreas Gruenbacher wrote:
> > Symlink /usr/bin/ptx (inode #110411) is invalid.
> > Clear<y>? no
> >
> > Entry 'ptx' in /usr/bin (110298) has an incorrect filetype (was 7,
> > should be 0).Fix<y>? no
> $ dd if=/dev/zero of=/image bs=4096 count=1024
> $ mke2fs -F -j /image
> $ mount -o loop /image /mnt
> # set labels ...
> $ umount /mnt
> $ bzip2 /image
--
Christopher J. PeBenito <pebenito@xxxxxxxx>
_______________________________________________
Ext3-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/ext3-users
