hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yoram Arnon" <yar...@yahoo-inc.com>
Subject RE: fsck with the move option
Date Mon, 01 May 2006 22:08:11 GMT
+1.
Files that are moved are inaccessible by normal means and there's little
reason to keep two copies of them around. A sys-admin could later either
remove them, or try to reassemble them and return them into place. Leaving
them in their original location just makes it harder to clean them up.

> -----Original Message-----
> From: Hairong Kuang [mailto:hairong@yahoo-inc.com] 
> Sent: Monday, May 01, 2006 2:53 PM
> To: hadoop-dev@lucene.apache.org
> Subject: fsck with the move option
> 
> After I read the fsck code, I realize that if we run fsck 
> with the move option, the tool actually copies the corrupted 
> files to "/lost+found" block by block. I feel that it is very 
> expensive especially with large corrupted file system. Shall 
> we simply do a rename, I mean, moving corrupted files to 
> "/lost+found"? Rename is a namespace mutation so it is much 
> more efficent.
>  
> Hairong
> 


Mime
View raw message