can't remove files in lost+found after fsck creates them on usb drive

[cracauer@]

If lost-and-found was created fsck was obviously running in read-write mode.

 

[tingo]

no guarantee - the lost+found directory might have been there already.

 

[bob2112]

Keep in mind that the files in lost+found are, by definition, corrupted.

That's not been my experience, most of mine have been intact files - often duplicates of files that are still present elsewhere.

 

[bakul]

In v7 unix lost+found got those inodes that had no dir. entries elsewhere but otherwise they had valid inode structure. These files would have the same probability of being corrupted as named files. I have not delved deeper into later filesystems to know what they actually do in fsck.