Re: Still wrong reported file size after --rebuild-tree

[reiser <reiser@namesys.com>]

Vitaly Fertman wrote:

>On Saturday 02 November 2002 00:07, Hans Reiser wrote:
>  
>
>>Vitaly Fertman wrote:
>>    
>>
>>>Hi,
>>>
>>>On Wednesday 30 October 2002 21:30, Philippe Gramoullé wrote:
>>>      
>>>
>>>>Hi,
>>>>
>>>>I just wanted to let you know that after rebuilding the tree for a 500Go
>>>>volume, i still have wrong file size reported :
>>>>
>>>>/dev/sdb1            572418604 174714996 397703608  31% /storage
>>>>
>>>># ls -l
>>>>total 4928006
>>>>-r-x-wx-wx 1 daemon   324231      32768 Jan  1  1970 25s.jpg
>>>>-r-x--x--- 1 19415372 19415373 83388383504122186 Aug 13 1970 25s_lb.jpg
>>>>-r--rw-rw- 1 19415354 19415355 83388306194710840 Aug 13 1970 25slight.jpg
>>>>-r---wxrwx 1 19415331 19415332 83388207410463009 Aug 13 1970
>>>>25slight_ln.jpg
>>>>        
>>>>
>>>ReiserFS can handle 64 bit file sizes, so from the reiserfsck point of
>>>view these are correct sizes.
>>>      
>>>
>>You mean to say that you haven't written code to check that file sizes
>>are correct, yes?
>>    
>>
>
>No, I meant that it is considered as a legal situation to have a size in 
>a file statdata greater then its real body size. Thus you can truncate 
>the file to the greater size. 
>
>However, if you are sure that you do not have files with such holes at 
>the end you can use --ajust-file-sizes option in rebuild and fix-fixable
>modes - fixable here - to correct such statdata's file sizes to file body 
>sizes. (Sorry that I have not mentioned about this option in my previous 
>email). 
>
>  
>
Ah, interesting.

Hans