"reiserfsck --rebuild-tree" taking daaays, what to do?

[JustinAiken]

- After replacing/rebuilding a failed hardware drive, the filesystem was still corrupt

- Started the array in maintenance mode

- Did a check through the WebUI, it told me to do `--rebuild-tree`

- Started the `--rebuild-tree` through the WebUI

- ..but now it's been running for 3 days, and I'm missing the array

- I started it through the UI, which added `--quiet`, so now I can't see too much of the progress; this morning it maed it to Pass 3 of Pass 3 (semantic), but the log hasn't moved for about 8 hours

 

root@Tower:/# ps aux |grep [r]eiser
root     11162  2.9  9.0 373176 362956 ?       D    Sep25  95:37 /sbin/reiserfsck /dev/md13 --yes --quiet --rebuild-tree

 

Is there a way to get the array/shares back while this finishes?

 

 

EDIT - More info:

 

Here's the log: https://gist.github.com/JustinAiken/fb84a4b62e2d6509743b65cd76809a32

 

...
vpf-10680: The file [4472 4481] has the wrong block count in the StatData (619528) - corrected to (496)
vpf-10680: The file [4472 4482] has the wrong block count in the StatData (630328) - corrected to (4176)
vpf-10680: The file [4472 4483] has the wrong block count in the StatData (599536) - corrected to (5152)
vpf-10680: The file [4472 4484] has the wrong block count in the StatData (606216) - corrected to (4536)
vpf-10680: The file [4472 4485] has the wrong block count in the StatData (752344) - corrected to (5336)
vpf-10680: The file [4472 4486] has the wrong block c

 

For some reason it cuts of mid-sentence, but the process is still running.

[JustinAiken]

Ahh, finally finished this morning!  I was getting worried this was going to be one of those 400 day things