[gentoo-user] e2fsck -c when bad blocks are in existing file?

[Grant Edwards]

I've got an SSD that's failing, and I'd like to know what files
contain bad blocks so that I don't attempt to copy them to the
replacement disk.

According to e2fsck(8):

       -c     This option causes e2fsck to use badblocks(8)  program  to  do  a
              read-only scan of the device in order to find any bad blocks.  If
              any bad blocks are found, they are added to the bad  block  inode
              to  prevent them from being allocated to a file or directory.  If
              this option is specified twice, then the bad block scan  will  be
              done using a non-destructive read-write test.

What happens when the bad block is _already_allocated_ to a file?

--
Grant