What has fsck -vcck done, to repair a partition?

[Ralf Mardorf]

Hi,

I already ordered a SSD to replace a fishy HDD. For the moment I run
fsck, since one file caused input/output errors when tar, cp or string
tried to read the file. When it failed, the HDD made click noises.
The file seemingly is repaired, but I don't understand what fsck has
done to repair it [1]. Any clues?

FWIW the Ubuntu that run fsck to repair /dev/sda9 is on another
HDD, it's /dev/sdb.

Regards,
Ralf

[1]
[weremouse at moonstudio ~]$ date; time sudo fsck -vcck /dev/sda9; date 
Fri Feb  3 15:32:57 CET 2017
[sudo] password for weremouse: 
fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
Checking for bad blocks (non-destructive read-write test)
Testing with random pattern: done                                                 
archlinux: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found.  Create<y>? yes
Pass 4: Checking reference counts
Pass 5: Checking group summary information

archlinux: ***** FILE SYSTEM WAS MODIFIED *****

     1962614 inodes used (54.33%, out of 3612672)
       57744 non-contiguous files (2.9%)
        1073 non-contiguous directories (0.1%)
             # of inodes with ind/dind/tind blocks: 71053/1016/0
    12471477 blocks used (86.37%, out of 14439168)
           0 bad blocks
           1 large file

     1662652 regular files
      264611 directories
           0 character device files
           0 block device files
           3 fifos
       12857 links
       35338 symbolic links (33323 fast symbolic links)
           0 sockets
------------
     1975461 files

real	60m19.059s
user	1m47.739s
sys	1m39.736s
Fri Feb  3 16:33:16 CET 2017
[weremouse at moonstudio ~]$ sudo mount -a
[sudo] password for weremouse: 
[weremouse at moonstudio ~]$ cp -ai /mnt/archlinux/usr/src/linux-rt-rosaplüsch/src/linux-4.9.6/net/sunrpc/.clnt.o.d
.clnt.o.d      .clnt.o.d.bak  
[weremouse at moonstudio ~]$ cp -ai /mnt/archlinux/usr/src/linux-rt-rosaplüsch/src/linux-4.9.6/net/sunrpc/.clnt.o.d /mnt/archlinux/usr/src/linux-rt-rosaplüsch/src/linux-4.9.6/net/sunrpc/.clnt.o.d.2bak
[weremouse at moonstudio ~]$ strings /mnt/archlinux/usr/src/linux-rt-rosaplüsch/src/linux-4.9.6/net/sunrpc/.clnt.o.d | head -1
AdminSocket: do_accept error: '
[weremouse at moonstudio ~]$ strings /mnt/archlinux/usr/src/linux-rt-rosaplüsch/src/linux-4.9.6/net/sunrpc/.clnt.o.d | head -2
AdminSocket: do_accept error: '
AdminSocket: error reading request code: 
[weremouse at moonstudio ~]$ rm /mnt/archlinux/usr/src/linux-rt-rosaplüsch/src/linux-4.9.6/net/sunrpc/.clnt.o.d*bak
[weremouse at moonstudio ~]$ ls /mnt/archlinux/usr/src/linux-rt-rosaplüsch/src/linux-4.9.6/net/sunrpc/.clnt.o.d*
/mnt/archlinux/usr/src/linux-rt-rosaplüsch/src/linux-4.9.6/net/sunrpc/.clnt.o.d
[weremouse at moonstudio ~]$ sudo rm -Ir /mnt/archlinux/lost+found/
rm: remove 1 argument recursively? y
[weremouse at moonstudio ~]$ ls /var/log/fsck/check
ls: cannot access '/var/log/fsck/check': No such file or directory
[weremouse at moonstudio ~]$ ls /var/log/fsck/check
checkfs    checkroot  
[weremouse at moonstudio ~]$ ls /var/log/fsck/checkfs 
/var/log/fsck/checkfs
[weremouse at moonstudio ~]$ less /var/log/fsck/checkfs 
[weremouse at moonstudio ~]$ cat /var/log/fsck/checkfs 
(Nothing has been logged yet.)
[weremouse at moonstudio ~]$ lsb_release -d
Description:	Ubuntu 16.04.1 LTS
[weremouse at moonstudio ~]$