Home | History | Annotate | Download | only in f_cloneblock_alloc_error
      1 Pass 1: Checking inodes, blocks, and sizes
      2 Inode 12, i_size is 0, should be 2015232.  Fix? yes
      3 
      4 
      5 Running additional passes to resolve blocks claimed by more than one inode...
      6 Pass 1B: Rescanning for multiply-claimed blocks
      7 Multiply-claimed block(s) in inode 13: 8
      8 Multiply-claimed block(s) in inode 14: 8
      9 Pass 1C: Scanning directories for inodes with multiply-claimed blocks
     10 Pass 1D: Reconciling multiply-claimed blocks
     11 (There are 2 inodes containing multiply-claimed blocks.)
     12 
     13 File /b (inode #13, mod time Wed Jan 21 03:41:55 2015) 
     14   has 1 multiply-claimed block(s), shared with 1 file(s):
     15 	/c (inode #14, mod time Wed Jan 21 03:42:37 2015)
     16 Clone multiply-claimed blocks? yes
     17 
     18 clone_file: Could not allocate block in ext2 filesystem returned from clone_file_block
     19 Couldn't clone file: Could not allocate block in ext2 filesystem
     20 Delete file? yes
     21 
     22 File /c (inode #14, mod time Wed Jan 21 03:42:37 2015) 
     23   has 1 multiply-claimed block(s), shared with 1 file(s):
     24 	/b (inode #13, mod time Wed Jan 21 03:41:55 2015)
     25 Multiply-claimed blocks already reassigned or cloned.
     26 
     27 Pass 2: Checking directory structure
     28 Entry 'b' in / (2) has deleted/unused inode 13.  Clear? yes
     29 
     30 Pass 3: Checking directory connectivity
     31 Pass 4: Checking reference counts
     32 Pass 5: Checking group summary information
     33 
     34 test_filesys: ***** FILE SYSTEM WAS MODIFIED *****
     35 test_filesys: 13/128 files (7.7% non-contiguous), 512/512 blocks
     36 Exit status is 1
     37