From: Piotr Szymaniak <szarpaj-TbOm9Ca2r9GrDJvtcaxF/A@public.gmane.org>
To: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: snapshots contain the same rrd database
Date: Wed, 26 Feb 2014 15:21:40 +0100 [thread overview]
Message-ID: <20140226142140.GD2022@wloczykij> (raw)
In-Reply-To: <1393422861.5481.9.camel@slavad-CELSIUS-H720>
[-- Attachment #1: Type: text/plain, Size: 1984 bytes --]
On Wed, Feb 26, 2014 at 05:54:21PM +0400, Vyacheslav Dubeyko wrote:
> Hi Piotr,
>
> On Wed, 2014-02-26 at 14:32 +0100, Piotr Szymaniak wrote:
> > Hi,
> >
> > I got a system crash after some 160+ days uptime. After a hard reboot I
> > noticed my rrd database looks corrupted.
> >
> > So I changed some recent checkpoints to snapshots, mounted them and...
> > all the rrd files are the same!
> >
>
> To be honest, I don't understand clearly:
> (1) How did you get the issue?
To me it looks like the file hasn't changed since the first boot. Like
it's not written at all? Is there a way to check something like "file
position" on disk in specific snapshot?
rrds are a bit weird databases. When created they are, ie. size A. And
all the way in time they gather some data and are always in that size A.
The size doesn't change. Maybe this is related?
> (2) Did you create snapshots after crash?
Yes.
> (3) Had you some snapshots before crash?
No.
> If you had a crash then you should have some error messages in the
> system log. Have you something? Or did you lose all error messages
> during the crash?
The crash was related to a process running on a different filesystem. My
syslog has only garbage, so yes, it is lost.
> Anyway, I need to have the reproducing path for investigate the issue.
> Of course, I am not going to wait 160 days before achieving the issue
> reproducibility. :) One of the possible way is to share some small
> NILFS2 volume with good issue reproducibility. But, currently, I don't
> quite follow in what way I can reproduce the issue.
I suppose this could be related to this "size A" mentioned above. Will
try to figure out some reproducibility path.
Piotr Szymaniak.
--
Jest tam jedno powiedzenie... nie pamietam go dokladnie, ale brzmi
mniej wiecej tak: "Czlowiek wyczuwajacy wiatr zmian winien budowac nie
oslony od wiatru, lecz mlyny".
-- Stephen King, "The Dead Zone"
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-02-26 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 13:32 snapshots contain the same rrd database Piotr Szymaniak
2014-02-26 13:54 ` Vyacheslav Dubeyko
2014-02-26 14:21 ` Piotr Szymaniak [this message]
2014-02-26 14:39 ` Vyacheslav Dubeyko
2014-02-27 2:45 ` Ryusuke Konishi
[not found] ` <20140227.114547.220041242.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2014-02-27 10:58 ` Piotr Szymaniak
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=20140226142140.GD2022@wloczykij \
--to=szarpaj-tbom9ca2r9grdjvtcaxf/a@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=slava-yeENwD64cLxBDgjK7y7TUQ@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