hadoop-mapreduce-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Harsh J <ha...@cloudera.com>
Subject Re: fsck -move is copying not moving
Date Fri, 13 Sep 2013 19:15:12 GMT
Hi,

The -move will move any existing good blocks (salvaging the file's
remains) under the specified file, to /lost+found/. This is regular
behavior. To get rid of a corrupt file entirely, a -delete or an -rm
-skipTrash is normally required.

On Sat, Sep 14, 2013 at 12:26 AM, alex bohr <alexjbohr@gmail.com> wrote:
> I have some corrupt blocks that I want to move to lost+found and work on
> recovering from the good blocks.
>
> So I ran
> hadoop fsck  /my/bad/filepath -move
>
> And it copied a bunch of files to lost+found/my/bad/filepath.  But the
> corrupt files are still at  /my/bad/filepath.
>
> Is that expected?  I thought fsck should Move not Copy the corrupt files.
>
> ... I then ran fsck  /my/bad/filepath -delete and it deleted the bad file so
> it's all fine, but that seems unnecessary.
>
> I'm on CDH3u5.
>
> Thanks



-- 
Harsh J

Mime
View raw message