On Tue, Dec 29, 2015 at 03:45:31PM +0530, Vignesh Raman wrote: > 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. > .... (a) what kernel and distribution version are you using? (b) can you reproduce this? If so, how? - Ted -- 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
