On Wed, 25 Oct 2000, peanut butter wrote:
>Yet, though I can't explain this, I believe I
>witnessed twice the oddity of constantly checking the directory size
>unchangingly and then, when convinced nothing was happening and so
>aborted amrecover, the directory size would "suddenly" 'du' as 20
>megs or so larger than the entire time I was checking it during the
>restore. Is there any reasonable explanation for this?
>
>So, I believe things were being restored but it was taking a
>painfully long time (yet, as a possibility you mentioned, the dump file
>itself was large, about 7 gigs) and eventhough I couldn't detect any
>increase in size of the directory being restored, after aborting the
>restore, the directory would be significantly larger.
Many file systems do not update the size value in an inode's directory
entry until the file is closed. You want to be watching the free space
drop in "df -k ." rather than watching "du thefile"
--
Joi Ellis
[EMAIL PROTECTED], http://www.visi.com/~gyles19/
