i have been using ext2ifs for 10 months, and after 500gb drive got full i got few I/O errors.
i booted linux, unmounted, and fsck'ed. after 4-5 days of cloning multiple blocks i got to
optimizing dirs and got segfault. after that i stupidly run fsck with -y option and it deleted my journal
after that i used differend available superblocks (-b x), and drive got more corruputed...
errors are currently so numerous that looking errors and pressing yes to questions would take many many hours.
fsck with -p option usually fails to cloning multiple blocks or error reading block x (Attempt to read block from
filesystem resulted in short read) while reading indirect blocks of inode y.
now i agree that fscking can be dangerous, for my mood & drive. my plans are buying another 500gb drive for raw backup
and searching/learning few weeks about data-backup, journal-backup and fscking. is this really necessary?
any good links would be nice 2 have.
p.s some info
# uname -a
Linux c-laptop 2.6.22-14-generic #1 SMP Tue Feb 12 02:46:46 UTC 2008 x86_64 GNU/Linux
# fdisk -l | grep sda4
/dev/sda4 974 60801 480568410 83 Linux
# dmesg | tail -n 3
[23871.163659] attempt to access beyond end of device
[23871.163668] sda: rw=0, want=753308173, limit=690022279
[23871.163674] Buffer I/O error on device sda4, logical block 184419231
# lsusb | grep West
Bus 003 Device 002: ID 1058:1001 Western Digital Technologies, Inc.