Hi,
On Tue, Dec 22, 2015 at 4:51 PM, Jan Kara <jack@xxxxxxx> wrote:
> It's hard to say why the fs got corrupted without more details. At least
> full fsck output, ideally image of the corrupted filesystem obtained via
> e2image.
The full e2fsck output is,
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix? yes
Inode 19387 was part of the orphaned inode list. FIXED.
Inode 19388 was part of the orphaned inode list. FIXED.
Inode 19390 was part of the orphaned inode list. FIXED.
Inode 19392 was part of the orphaned inode list. FIXED.
Inode 19396 was part of the orphaned inode list. FIXED.
Inode 19399 was part of the orphaned inode list. FIXED.
Inode 19401 was part of the orphaned inode list. FIXED.
Inode 19405 was part of the orphaned inode list. FIXED.
Inode 19414 was part of the orphaned inode list. FIXED.
Inode 19416 was part of the orphaned inode list. FIXED.
Inode 19873 was part of the orphaned inode list. FIXED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/mnt/test/test.img: ***** FILE SYSTEM WAS MODIFIED *****
20129 inodes used (31.44%)
25 non-contiguous files (0.1%)
4 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 20119/1
694365 blocks used (75.34%)
0 bad blocks
1 large file
19973 regular files
147 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
20120 files
Regards,
Vignesh.
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
