On 01/08/2011 02:31 PM, Sebastian Hyrwall wrote:
Hi
Hello.
I am getting a negative block-number with reiserfsck when doing --rebuild-tree -S (or without -S). This causes a segmentation fault later (pass 2) in the check because it tries to read a "non-existant block". My rebuild takes 3 days and i didn't copy the stdout-info the first time so I will post some more info as soon as it becomes available. Pass 0: ####### Pass 0 ####### The whole partition (-710934672 blocks) is to be scanned Skipping 117586 blocks (super block, journal, bitmaps)
So you do have a ~16T partition. Correct? -711052258 blocks
will be read Does anyone have any idea on how to fix this? On a 64-bit system.
It looks like you have encountered an overflow/truncation fsck bug specific to giant volumes.
I would first ask Jeff: AFAIK he is planning to enable 16T files in reiserfs. Jeff, do you have any non-published fixups for such problems? Thanks, Edward.
Sincerely, Sebastian H -- To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
-- To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
