howto speed up fsck.ext3?
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:
Thanks for any sugguestion and comments. All the best, joseph |
Bump***
It's still running there, which have been using more than 7 days :( |
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.
|
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 |
Sorry I couldn't be of more help. What other method are you using and where did you find it ?
|
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. |
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. |
All times are GMT -5. The time now is 03:23 AM. |