Hi :-) I have a root nilfs partition that appears to have been corrupted. When I try to mount the partition - either on boot or with a liveusb - I'm getting "NILFS: corrupt root inode". I don't believe anything too exciting happened on the last shutdown, but it's entirely possible that the umount/sync command didn't execute correctly. I've tried mounting with with two kernels, being 3.9 and 3.9.4 In the first case nilfs is built in, in the second it's a module. This is an x86_64 laptop. I was hoping someone might be able to offer some help with trying to recover the partition :-) I'm happy to provide any useful info from the drive :-) Cheers :-) Bryce nilfs-tune -l /dev/loop4 -------------------------- nilfs-tune 2.1.5 Filesystem volume name: (none) Filesystem UUID: fb7fe0c7-f6ef-44e9-8fd7-0125801e5f36 Filesystem magic number: 0x3434 Filesystem revision #: 2.0 Filesystem features: (none) Filesystem state: valid Filesystem OS type: Linux Block size: 4096 Filesystem created: Fri Aug 17 00:26:09 2012 Last mount time: Sat Jun 22 04:18:22 2013 Last write time: Sun Jun 23 01:00:59 2013 Mount count: 691 Maximum mount count: 50 Reserve blocks uid: 0 (user root) Reserve blocks gid: 0 (group root) First inode: 11 Inode size: 128 DAT entry size: 32 Checkpoint size: 192 Segment usage size: 16 Number of segments: 269 Device size: 2264924160 First data block: 1 # of blocks per segment: 2048 Reserved segments %: 5 Last checkpoint #: 373808 Last block address: 405504 Last sequence #: 568326 Free blocks count: 73728 Commit interval: 0 # of blks to create seg: 0 CRC seed: 0x44983069 CRC check sum: 0xced8962d CRC check data size: 0x00000118 -- Bryce Gibson bryce@xxxxxxxxxxxxxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
