Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
MapReduce >> mail # user >> fsck -move is copying not moving

Copy link to this message
Re: fsck -move is copying not moving

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 <[EMAIL PROTECTED]> 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