On Thu, October 25, 2007 13:35, Ameet Nanda wrote: > I unmounted /dev/sda2 and ran fsck.ext3. this was the complete o/p thanks for the log. Now the real gurus have something to work with :-) > root@172:/root> fsck.ext3 /dev/sda2 -v -n > e2fsck 1.40.2 (12-Jul-2007) /dev/sda2 contains a file system with errors, > check forced. If the filesystem is corrupted, all kinds of things might happen to your .tar file. A good start would be to find out what could've caused the filesystem corruptions in the first place. Did your box lose power and crashed? Has the hardware been altered, new memory, new cables? > Oct 25 17:16:53 172 kernel: [ 267.117373] attempt to access beyond end > of device > Oct 25 17:16:53 172 kernel: [ 267.117396] sda2: rw=0, want=13777058744, > limit=48195000 Did someone/something alter the partition table? Can you do the following without getting errors in kern.log? dd if=/dev/sda2 of=/dev/null bs=512 Christian. -- BOFH excuse #442: Trojan horse ran out of hay _______________________________________________ Ext3-users mailing list Ext3-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ext3-users
