October 23, 20178 yr So this is the second time this happened to me, when running reiserfsck --rebuild-tree, it appears to 'finish': ####### Pass 3a (lost+found pass) ######### Looking for lost directories: Looking for lost files:0 /sec vpf-10680: The file [3898 3899] has the wrong block count in the StatData (25216) - corrected to (7960) Flushing..finished Objects without names 131 Files linked to /lost+found 131 Pass 4 - finishedne 108265, 18044 /sec Deleted unreachable items 16433 Flushing..finished Syncing..finished But the application never actually terminates. It appears to just hang indefinitely. The first time, I let it sit for just over 24 hours, hoping it would eventually timeout -- but no dice. Am I being impatient? Should it really take this long, or is something else amiss? The first time (and only other time I've had to rebuild-tree), I killed the process -- which, unsurprisingly, resulted in a zombie process. It was on an non-important array, so I wound up just chucking it and starting over. This one, however, I'd prefer to keep intact.. root@aenima:~# ps aux |grep "[r]eiserfsck" root 6298 5.4 0.3 126480 121784 pts/1 D+ 08:24 37:22 reiserfsck --rebuild-tree /dev/md7 I can't imagine it matters, but I am running this inside a screen process.. Any thoughts? Edited October 23, 20178 yr by magn2o
Archived
This topic is now archived and is closed to further replies.