Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Data recovery



James Kramer wrote:
>And don't use fsck. Use e2fsck for an ext3 system. Fsck is what comes
>up first when your system crashes, but say no, escape, reboot with
>rescue disk and use the afor mentioned e2fsck.

I see this in the fsck man page:

    In actuality, fsck is simply a front-end for the various file
    system checkers (fsck.fstype) available under Linux.  The file
    system-specific checker is searched for in /sbin first, then in
    /etc/fs and /etc, and finally in the directories listed in the
    PATH environment variable.  Please see the file system-specific
    checker manual pages for further details.

also I note       

  vanzandt:/var/mail $ ls -il /sbin/*fsck*|sort
  57966599 -rwxr-xr-x  3 root root 130152 Aug 22 00:55 /sbin/e2fsck
  57966599 -rwxr-xr-x  3 root root 130152 Aug 22 00:55 /sbin/fsck.ext2
  57966599 -rwxr-xr-x  3 root root 130152 Aug 22 00:55 /sbin/fsck.ext3
  57966606 -rwxr-xr-x  1 root root  18208 Aug 22 00:55 /sbin/fsck
  ...

so e2fsck is actually the same file as fsck.ext3, which will be called
by fsck for an ext3 filesystem.  Are you saying that ignoring the
journal improves the filesystem check?  I would expect that to
increase the number of inconsistencies in the metadata.

                  - Jim Van Zandt




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org