On Mon, 13 Jun 2011 16:28:19 -0700, Zahid Chowdhury wrote:
> Hello Dexen/Ryusuke,
> Thanks both for your help. I tried this:
>[quadcore:~/nilfs/nilfs-utils.git/nilfs2-utils] git fetch
>http://git.nilfs.org/nilfs2-utils-devel.git fsck0:fsck0
>fatal: Refusing to fetch into curre
Hello Dexen/Ryusuke,
Thanks both for your help. I tried this:
[quadcore:~/nilfs/nilfs-utils.git/nilfs2-utils] git fetch
http://git.nilfs.org/nilfs2-utils-devel.git fsck0:fsck0
fatal: Refusing to fetch into current branch
[quadcore:~/nilfs/nilfs-utils.git/nilfs2-utils] git chec
Hi again Zahid,
On Tuesday 14 June 2011 00:21:51 I wrote:
> $ git co -b fsck0 remotes/origin/fsck0
important correction: make that last line read:
$ git checkout -b fsck0 remotes/origin/fsck0
(`co' is not a git command, `checkout' is)
Sorry for the screw-up,
--
dexen deVries
``One can't pr
Hi Zahid,
On Monday 13 June 2011 23:12:00 you wrote:
> 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
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-fetc
On Monday 13 June 2011 16:40:48 you wrote:
> So, you hit the bug on a raw hadrware.
> In my hardware, /sys/kernel/mm/cleancache/* didn't change.
which most probably means you haven't had zcache enabled, due to the bug in
its build system (as described in prev mail).
Attached is the silly patch
Hi Ryusuke,
On Monday 13 June 2011 16:40:48 you wrote:
> So, you hit the bug on a raw hadrware.
> In my hardware, /sys/kernel/mm/cleancache/* didn't change.
>
> Is it reproducible without zcache?
>
> If not, we should share the steps with zcache.
I think I've got it reproductable. I believe i
On Mon, 13 Jun 2011 15:21:15 +0200, dexen deVries wrote:
> Hi Ryusuke,
>
>
> On Monday 13 of June 2011 15:15:03 you wrote:
> > I couldn't reproduce this problem.
> > Could you tell me more about how you did it.
> >
> > May I reproduce the oops on native machines ? (I mean non-virtual
> > machine
On Monday 13 of June 2011 13:30:39 you wrote:
> > it seems only two of the above commits were pulled; the ``fix problem in
> > setting checkpoint interval'' is missing from Linus' repo as of now.
>
> Linus has not yet pulled any commits.
> Just wait a day or so.
thanks for clarification; turns o
Hi Ryusuke,
On Monday 13 of June 2011 15:15:03 you wrote:
> I couldn't reproduce this problem.
> Could you tell me more about how you did it.
>
> May I reproduce the oops on native machines ? (I mean non-virtual
> machine environment).
I'll try to re-create the condition today; been busy throug
Hi dexen,
On Wed, 08 Jun 2011 23:02:31 +0900 (JST), Ryusuke Konishi wrote:
> On Wed, 8 Jun 2011 15:14:59 +0200, dexen deVries wrote:
> > Hi list,
> >
> >
> > there's that recent interesting addition to linux: `cleancache' (and
> > `zcache').
> > I've enabled it for NILFS2 yesterday (in 3.0-rc2).
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 F
On Mon, 13 Jun 2011 10:39:42 +0200, dexen deVries wrote:
> Hi Ryusuke,
>
>
> On Monday 13 of June 2011 06:16:59 you wrote:
> > Hi Linus,
> >
> > please pull from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2.git
> > for-linus
> >
> > to receive the following bug fixes
Hi Ryusuke,
On Monday 13 of June 2011 06:16:59 you wrote:
> Hi Linus,
>
> please pull from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2.git
> for-linus
>
> to receive the following bug fixes. These fix a reported bug and two
> boundary condition bugs recently found in b
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
15 matches
Mail list logo
