Hello Ryusuke (or anybody else),
I am no git expert, just looked at the cheatsheet, but I was unable to find
your commit which add's a reason to the message below. I tried:
git pull http://git.nilfs.org/nilfs2-utils-devel.git fsck0:fsck0
Already up-to-date.
I also tried a re-fetch from scratch. All with no changes showing up in
fsck0.nilfs2.c. If anybody else knows a way for me to pickup Ryusuke's commit,
please let me know. Thanks.
Zahid
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Ryusuke Konishi
Sent: Monday, June 13, 2011 5:33 AM
To: Zahid Chowdhury
Cc: [email protected]
Subject: Re: mount & fsck of nilfs partition fail.
On Mon, 13 Jun 2011 00:13:17 -0700, Zahid Chowdhury wrote:
> Hello,
> We had another crash with nilfs2 under load and then on reboot mount failed
> as usual on
> "Checksum error in segment payload"
> Leter when we tried an "fsck0.nilfs2 -v -f" on the partition we got:
> .
> .
> .
> Unclean FS.
> The latest log is lost. Trying rollback recovery..
> .
> Searching the latest checkpoint.
> fsck0.nilfs2: cannot read block (blocknr = 2696911)
>
> and fsck0.nilfs2 gave up. Is there any other way of recovering this
> partition? If so, how?
Seems an I/O error or some sort of critical error happened.
I pushed a commit to append error reason in the above message.
Could you try it ? (it's available on the fsck0 branch of the devel tree).
> Is this problem common? Is there any way to stop this scenario from
> occurring? Thanks.
>
> Zahid
Regards,
Ryusuke Konishi
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
