*sigh* Just realised that that's the wrong segment... The dumpseg for the last block address segment (405504) is below; ` dumpseg /dev/loop3 $((405504 / 2048 )) ` Apologies for the spaminess :-( segment: segnum = 198 sequence number = 568326, next segnum = 199 partial segment: blocknr = 405504, nblocks = 13 creation time = 2013-06-23 01:00:59 nfinfo = 1 finfo ino = 3, cno = 0, nblocks = 11, ndatblk = 0 blkoff = 255, level = 1, blocknr = 405505 blkoff = 510, level = 1, blocknr = 405506 blkoff = 2295, level = 1, blocknr = 405507 blkoff = 3570, level = 1, blocknr = 405508 blkoff = 4590, level = 1, blocknr = 405509 blkoff = 4845, level = 1, blocknr = 405510 blkoff = 5100, level = 1, blocknr = 405511 blkoff = 5355, level = 1, blocknr = 405512 blkoff = 5610, level = 1, blocknr = 405513 blkoff = 5738, level = 1, blocknr = 405514 blkoff = 0, level = 2, blocknr = 405515 -- Bryce Gibson bryce@xxxxxxxxxxxxxxxxxxxxxxxx On Mon, Jun 24, 2013, at 02:37 PM, Bryce Gibson wrote: > Ps, > I've attached the output of `dumpseg /dev/loop4 0 > dumpseg.txt` incase > it helps :-) > > Cheers again, > Bryce > > -- > Bryce Gibson > bryce@xxxxxxxxxxxxxxxxxxxxxxxx > > On Mon, Jun 24, 2013, at 01:19 PM, Bryce Gibson wrote: > > 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 > Email had 1 attachment: > + dumpseg.txt > 88k (text/plain) -- 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
