You won't usually get a reliable result from e2fsck without unmounting the filesystem first. Since's it appears that this is the /home partition, maybe you should logout all normal users and umount /home and rerun e2fsck to make sure there REALLY are no errors on the filesystem. ReiserFS works beautifully on 4.2.1 btw and there is no need to run a fs check on journaling file systems (99.9999% of the time :-) )
- Tom Walker -----Original Message----- From: Christian Glaser [mailto:[EMAIL PROTECTED]] Sent: Friday, March 22, 2002 9:51 AM To: [EMAIL PROTECTED] Subject: linux TSM4.2.1: backup problem w/ ext2 hello all, i have a problem with my linux-client, TSM-server is 4.1.4 -------------------- [urmel@moby urmel]$ uname -a Linux moby.ae.go.dlr.de 2.4.9-6custom #1 SMP Tue Oct 30 11:41:02 CET 2001 i686 unknown [urmel@moby urmel]$ dsmc Tivoli Storage Manager Command Line Backup Client Interface - Version 4, Release 2, Level 1.0 (C) Copyright IBM Corporation, 1990, 2001, All Rights Reserved. --------------------- i recently noticed this entries in my dsmerror.log: ------------------ 03/21/2002 16:51:05 TransErrno: Unexpected error from lstat, errno = 9 ----------------- after some investigation it was clear that some files/dirs never got backed up following this error-msgs. this error seems to inidcate a bad filedescriptor. so i made a filesystemcheck assuming the error there. ---------------------- [root@moby /root]# fsck /dev/hda5 Parallelizing fsck version 1.23 (15-Aug-2001) e2fsck 1.23, 15-Aug-2001 for EXT2 FS 0.5b, 95/08/09 /dev/hda5 is mounted. WARNING!!! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage. Do you really want to continue (y/n)? yes /home was not cleanly unmounted, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /home: 33232/2424832 files (43.4% non-contiguous), 4580356/4843589 blocks -------------------------- nothing suspicious here. i thought the error must be on client-system side as it is an error by the 'lstat' system function. but how come that the fsck went fine and no other programs are compaining - at least as far as i noticed it yet. any hel appreciated. best regards / mit freundlichen gruessen christian glaser _____________________________________________________________________ T-systems Solutions for Research GmbH c/o DLR - 8234 oberpfaffenhofen tel: ++49 +8153/28-1156 e-mail: [EMAIL PROTECTED] fax: 28-1136 This e-mail including any attachments is confidential and may be legally privileged. If you have received it in error please advise the sender immediately by return email and then delete it from your system. The unauthorized use, distribution, copying or alteration of this email is strictly forbidden. This email is from a unit or subsidiary of EMI Recorded Music, North America
