linux-nilfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Piotr Szymaniak <szarpaj-TbOm9Ca2r9GrDJvtcaxF/A@public.gmane.org>
To: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
Cc: Ryusuke Konishi
	<konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>,
	linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: NILFS: corrupt root inode after Turbo Mode?
Date: Wed, 24 Oct 2012 09:36:41 +0200	[thread overview]
Message-ID: <20121024073641.GB27763@wloczykij> (raw)
In-Reply-To: <1350999330.2041.48.camel@slavad-ubuntu>

[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]

On Tue, Oct 23, 2012 at 05:35:30PM +0400, Vyacheslav Dubeyko wrote:
> I think that the issue is the concrete SD-card's issue. So, if you
> simply dump out the image on another SD-card then, I hope, all will work
> fine.

But what could be the issue with SD-card?

Anyway, I did a second image, mounted it as before and it works. dmesg
shows:
[ 2740.544690] NILFS warning: broken superblock. using spare superblock (blocksize = 1024).
[ 2740.544754] NILFS warning: broken superblock. using spare superblock (blocksize = 4096).
[ 2740.544760] NILFS warning: mounting unchecked fs
[ 2740.861477] NILFS: recovery complete.
[ 2740.911019] segctord starting. Construction interval = 300 seconds, CP frequency < 30 seconds

I will try to put the image after mount/umount back to the SD-card and
check if it works on Raspberry Pi.


Piotr Szymaniak.
-- 
 - (...) Nie wyobrazam sobie, co ta gora miesa moglaby ci dac, czego ja
nie   moglbym   ofiarowac.  Oczywiscie  poza  piecdziesiecioma  funtami
rozrosnietych miesni.
 - Moze mnie wlasnie pociagaja rozrosniete miesnie. (...) W koncu wielu
mezczyzn pociaga rozrosnieta tkanka tluszczowa piersi.
  -- Graham Masterton, "The Wells of Hell"

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-10-24  7:36 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-08 22:25 NILFS: corrupt root inode after Turbo Mode? Piotr Szymaniak
2012-10-09  7:29 ` Vyacheslav Dubeyko
2012-10-09 10:52   ` Piotr Szymaniak
2012-10-09 12:08     ` Vyacheslav Dubeyko
2012-10-09 13:58       ` Piotr Szymaniak
2012-10-09 16:24         ` Ryusuke Konishi
     [not found]           ` <20121010.012440.17932600.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2012-10-09 17:32             ` Vyacheslav Dubeyko
2012-10-10  7:39             ` Piotr Szymaniak
2012-10-10 10:43               ` Vyacheslav Dubeyko
2012-10-10 20:39                 ` Piotr Szymaniak
2012-10-10 12:03               ` Vyacheslav Dubeyko
2012-10-10 22:03                 ` Piotr Szymaniak
2012-10-11  6:50                   ` Vyacheslav Dubeyko
2012-10-11  9:23                     ` Piotr Szymaniak
2012-10-11 10:12                       ` Vyacheslav Dubeyko
2012-10-11 18:03                         ` Piotr Szymaniak
2012-10-12  7:10                           ` Vyacheslav Dubeyko
2012-10-12 10:31                             ` Piotr Szymaniak
2012-10-12 11:07                               ` Vyacheslav Dubeyko
2012-10-12 11:40                                 ` Piotr Szymaniak
2012-10-14 14:55                                   ` Vyacheslav Dubeyko
     [not found]                                     ` <26EBDBC2-8938-41BC-8C0C-6F6F3A0FD1EC-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2012-10-14 20:47                                       ` Piotr Szymaniak
2012-10-15  5:58                                         ` Vyacheslav Dubeyko
2012-10-18 12:29                                         ` Vyacheslav Dubeyko
     [not found]                                     ` <20121014200836.GK27763@wloczykij>
2012-10-15  6:18                                       ` Vyacheslav Dubeyko
2012-10-18 20:15                                         ` Piotr Szymaniak
2012-10-19  6:43                                           ` Vyacheslav Dubeyko
2012-10-19 10:14                                             ` Piotr Szymaniak
2012-10-23  6:31                                               ` Vyacheslav Dubeyko
2012-10-23  8:41                                                 ` Piotr Szymaniak
2012-10-23  9:26                                                   ` Vyacheslav Dubeyko
2012-10-23 11:54                                                     ` Piotr Szymaniak
2012-10-23 13:35                                                       ` Vyacheslav Dubeyko
2012-10-24  7:36                                                         ` Piotr Szymaniak [this message]
2012-10-25 12:13                                                           ` Vyacheslav Dubeyko
2012-10-12 11:49     ` Christian Smith
     [not found]       ` <20121012114915.GE7823-Ng8wz+J301SNY5Lh21HnMTHS2PGA244I9dF7HbQ/qKg@public.gmane.org>
2012-10-12 12:28         ` Piotr Szymaniak
2012-10-12 20:56     ` Piotr Szymaniak
2012-10-09 11:53   ` 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=20121024073641.GB27763@wloczykij \
    --to=szarpaj-tbom9ca2r9grdjvtcaxf/a@public.gmane.org \
    --cc=konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@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;
as well as URLs for NNTP newsgroup(s).