Linux NILFS development
 help / color / mirror / Atom feed
From: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
To: Piotr Szymaniak <szarpaj-TbOm9Ca2r9GrDJvtcaxF/A@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Time issues with checkpoints resolved?
Date: Wed, 30 Jan 2013 09:50:07 +0400	[thread overview]
Message-ID: <1359525007.2085.10.camel@slavad-ubuntu> (raw)
In-Reply-To: <20130129221021.GL10316@wloczykij>

Hi Piotr,

On Tue, 2013-01-29 at 23:10 +0100, Piotr Szymaniak wrote:
> Hi,
> 
> Sorry, but I can't find an answer and noticed some checkpoints in the
> past in the middle of other checkpoints (there was a thread, I think,
> about similar issue with timezone change).
> 
> Right now I have (Raspberry Pi doesn't have RTC):
> ~ lscp
> (...)
> 7870  2013-01-27 15:12:30   cp    -           22      42174
> 7871  2013-01-27 15:34:23   cp    -           19      42174
> 7872  2013-01-27 15:42:29   cp    -           22      42174
> 7873  1970-01-01 01:05:05   cp    -           93      42176
> 7874  1970-01-01 01:10:05   cp    -           22      42174
> 7875  1970-01-01 01:36:36   cp    -           18      42174
> (...)
> 8031  1970-01-03 07:08:19   cp    -           57      42183
> 8032  1970-01-03 07:13:20   cp    -           36      42182
> 8033  2013-01-29 00:01:57   cp    -           30      42182
> 8034  2013-01-29 00:19:34   cp    -          599      42313
> 
> I just wonder if cleaner is now smart enough to clean this mess.
> 

Unfortunately, it is not. Such fix doesn't made yet. I think that it
needs to modify nilfs-clean utility. But, currently, I am deeply inside
fixing of issues with flush kernel thread and bad btree node. These
issues are slightly complex. I tried several solutions but I haven't the
proper yet. Maybe, a final solution will be a combination of several
fixes that I tried.

But fixing of issue with timezone change in my TODO list.

With the best regards,
Vyacheslav Dubeyko.

> 
> Piotr Szymaniak.


--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-01-30  5:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 22:10 Time issues with checkpoints resolved? Piotr Szymaniak
2013-01-30  5:50 ` Vyacheslav Dubeyko [this message]
2013-02-12  9:29   ` Piotr Szymaniak
2013-02-13  6:24     ` Vyacheslav Dubeyko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1359525007.2085.10.camel@slavad-ubuntu \
    --to=slava-yeenwd64clxbdgjk7y7tuq@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=szarpaj-TbOm9Ca2r9GrDJvtcaxF/A@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox