All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Bezrukov <nilfs-issues-tvrqcU/I3+LBxmVkcvZ8vQ@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Corrupted nilfs2 volume
Date: Tue, 19 Mar 2013 02:31:45 +0400	[thread overview]
Message-ID: <20130318223145.GA17965@black> (raw)
In-Reply-To: <4E5BDA60-7615-4F82-AC0F-4459DD9EF544-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>

Hi Vyacheslav,

thank you for your analysis and support!

> As I can see from the debug output last write was on Friday
> March 15, 2013 at 00:02:24.

This write (unless something has happened to system clock) must have
occured during the mount attempt after the reboot. The time you
mention (which timezone, btw?) is approximately the time when I
discovered that my laptop has hung and when I rebooted it. My
impression (which may be wrong) is that there passed quite a while
after the hang before I had noticed this.

> So, I need in raw dump of three segments #23443 (ss_seq = 305301,
> first block #48011264), #23444 (ss_seq = 305302, first block
> #48013312), #23445 (ss_seq = 305303, first block #48015360).
> Please, make raw dump from #48011264 till #48017408 (namely,
> 6144 blocks)

A small note: 48017408-48011264+1 = 6145

> and share with me. Moreover, please, share dumpseg output
> for this segments.

I prepared the dumpseg output for these segments. Please find it
at http://www.dragonworks.ru/nilfs2/dumpseg.log .

As to the raw data, these blocks happened to contain some quite
sensitive information. I won't share this information
publicitly and would avoid leaking it as much as it seems
reasonable. If this data is of real and great help, please
let me know, I will prepare and send a link privately.
Sorry about that.

> Tomorrow, I prepare patch with additional debug output for
> deeper investigation of the issue on your side.

Is there any chance to register a different fs aside with
"official" nilfs2? Would such a simple change be sufficient?

diff -ur org/super.c new/super.c
--- org/super.c	2013-03-19 02:17:23.922469000 +0400
+++ new/super.c	2013-03-19 02:16:20.440634698 +0400
@@ -1356,7 +1356,7 @@
 
 struct file_system_type nilfs_fs_type = {
 	.owner    = THIS_MODULE,
-	.name     = "nilfs2",
+	.name     = "nilfs2-dbg",
 	.mount    = nilfs_mount,
 	.kill_sb  = kill_block_super,
 	.fs_flags = FS_REQUIRES_DEV,

What I want is to whenever possible avoid rebooting a machine
I am using for experimentation. It has /home on a nilfs2
partition and there're usually open user files on it.

Thanks and regards.
Alexander Bezrukov.
--
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

  parent reply	other threads:[~2013-03-18 22:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130315024019.7DC1BD00@mail.dragonworks.ru>
     [not found] ` <20130315024019.7DC1BD00-foQFVU7ZUqen8/iIaQqUdCjHesifYMBh@public.gmane.org>
2013-03-15  6:21   ` Corrupted nilfs2 volume Vyacheslav Dubeyko
2013-03-15 23:21     ` Alexander Bezrukov
2013-03-16 15:11       ` Vyacheslav Dubeyko
     [not found]         ` <70219EF1-8083-4DD5-BA18-84CD1914DC3E-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-03-18 14:23           ` Alexander Bezrukov
2013-03-18 20:44             ` Vyacheslav Dubeyko
     [not found]               ` <4E5BDA60-7615-4F82-AC0F-4459DD9EF544-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-03-18 22:31                 ` Alexander Bezrukov [this message]
2013-03-19  8:06                   ` Vyacheslav Dubeyko
2013-03-19  8:30                     ` ARAI Shun-ichi
     [not found]                       ` <20130319.173020.3478740326553917.hermes-akuOmOme3sQYOdUovKs6ag@public.gmane.org>
2013-03-19  9:15                         ` Vyacheslav Dubeyko
     [not found]                           ` <20121130.164616.1703426007244850753.hermes-akuOmOme3sQYOdUovKs6ag@public.gmane.org>
2013-03-19 11:17                             ` ARAI Shun-ichi
     [not found]                               ` <20130319.201730.1543938923107719972.hermes-akuOmOme3sQYOdUovKs6ag@public.gmane.org>
2013-03-19 11:42                                 ` Vyacheslav Dubeyko
2013-03-19 12:52                                   ` ARAI Shun-ichi
2013-03-19 17:35                     ` Alexander Bezrukov
2013-03-21  6:31                       ` 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=20130318223145.GA17965@black \
    --to=nilfs-issues-tvrqcu/i3+lbxmvkcvz8vq@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.