I am using Linux robot1 3.12.3-1-ARCH #1 SMP PREEMPT Wed Dec 4 21:45:42 CET 2013 x86_64 GNU/Linux Is that an "old" kernel? Also, note that an "old" kernel (from February this year) could mount this image, whereas this newer kernel hung. Is that consistent with the changes you have done? Sincerely, jw Sincerely, Jon Watte -- "I pledge allegiance to the flag of the United States of America, and to the republic for which it stands, one nation indivisible, with liberty and justice for all." ~ Adopted by U.S. Congress, June 22, 1942 On Sat, Dec 7, 2013 at 2:34 AM, Vyacheslav Dubeyko <slava@xxxxxxxxxxx> wrote: > > On Dec 7, 2013, at 5:17 AM, Jon Watte wrote: > > [snip] >> However, yesterday when booting up agian, it refused to mount the root >> disk, and booting was halted, with the messages shown in the below >> photograph. Note that, because I can't boot, I can't get this output >> in a copy-and-paste-able form! >> >> https://pbs.twimg.com/media/BaxOmptCYAABQuW.jpg:large >> >> The two repeated messages are (typed in from the photo): >> NILFS: bad bree node (blocknr=1364234) ; level = 100; flags = 0x73; >> nchildren = 12336 >> NILFS error (device sda1): nilfs_bmap_lookup_contig: broken bmap >> (inode number=3935) > > What linux kernel version do you have? > > I had fixed the reason of such problem by patch [1]. So, please check and > share your kernel version, firstly. I suppose that you are simply using old > kernel version. > > With the best regards, > Vyacheslav Dubeyko. > > [1] http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/3082 > -- 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
