howto speed up fsck.ext3?

edenCC · 01-14-2009, 09:45 PM

Hi, List,
Days before, I dumped a disk volume by "dd", which has a size of 250GB.

Then I issued "fsck.ext3" to check this corrupted file-system, but it already took one whole week, and it's still running there with very little output. When I use strace, it says sth. like this:

Quote:

_llseek(5, 76238565376, [76238565376], SEEK_SET) = 0
read(5, "\304\2\34\1\305\2\34\1\316\2\34\1\317\2\34\1\305!\34\1"..., 4096) = 4096
_llseek(5, 76300566528, [76300566528], SEEK_SET) = 0
read(5, "\345=\34\1\346=\34\1\347=\34\1\350=\34\1\361=\34\1\362"..., 4096) = 4096
_llseek(5, 76510662656, [76510662656], SEEK_SET) = 0
read(5, "B\6\35\1C\6\35\1D\6\35\1E\6\35\1F\6\35\1G\6\35\1H\6\35"..., 4096) = 4096
_llseek(5, 76510830592, [76510830592], SEEK_SET) = 0
read(5, "k\6\35\1l\6\35\1m\6\35\1n\6\35\1o\6\35\1p\6\35\1q\6\35"..., 4096) = 4096
_llseek(5, 76522594304, [76522594304], SEEK_SET) = 0
read(5, "\243\21\35\1\244\21\35\1\245\21\35\1\246\21\35\1\247\21"..., 4096) = 4096
_llseek(5, 80347250688, [80347250688], SEEK_SET) = 0

So, my question is how can I speed up an fsck instance, frankly I cannot wait any longer because I need to recover the production environment a.s.a.p, damn it!
Thanks for any sugguestion and comments.

All the best,
joseph

edenCC · 01-15-2009, 07:54 PM

Bump***

It's still running there, which have been using more than 7 days

asymptote · 01-15-2009, 11:28 PM

Dude you gotta move on. I was thinking about replying to this yesterday and I elected not too because I don't understand the output that you posted but seriously - you gotta move on. I have a 250 GB (as you can see in my sig) and it takes a couple of minutes to run fsck. Either your machine is not running the process properly or it's corrupted beyond belief.

edenCC · 01-18-2009, 08:19 AM

Hi, asymptote, Thanks for your note.
Luckily I have used another way to recover the corrupted fs(the fsck.ext3 is just checking a dd image, not the real file-system), so I would let the fsck.ext3 keep running, and wanna find out how many days it would use.

Regards - joe

asymptote · 01-18-2009, 08:25 AM

Sorry I couldn't be of more help. What other method are you using and where did you find it ?

edenCC · 01-20-2009, 12:17 AM

I just simply migrated all the "normal" files from the corrupted partition to a new partition.
Luckily nearly all the files recovered.

Tips to verify a normal file:
1, compare the outputs from these two commands: "ls -l filename" and "du -sh filename". It will get rid of sparse files.
2, using "wc filename" to get rid of files that have "internal" errors.

edenCC · 01-20-2009, 12:17 AM

I just simply migrated all the "normal" files from the corrupted partition to a new partition.
Luckily nearly all the files recovered.

Tips to verify a normal file:
1, compare the outputs from these two commands: "ls -l filename" and "du -sh filename". It will get rid of sparse files.
2, using "wc filename" to get rid of files that have "internal" errors.