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: NILFS: corrupt root inode after Turbo Mode?
Date: Tue, 09 Oct 2012 11:29:53 +0400 [thread overview]
Message-ID: <1349767793.3427.7.camel@slavad-ubuntu> (raw)
In-Reply-To: <20121008222557.GU28032@wloczykij>
Hi,
On Tue, 2012-10-09 at 00:25 +0200, Piotr Szymaniak wrote:
> Hi list.
>
> I'm using nilfs2 on my Raspberry Pi rootfs. I've played around with
> Raspberry Pi Turbo Mode and today it refused to boot. It's a headless
> setup so I moved the SD Card to my other machine and tried to mount
> rootfs partition:
>
As I can understand Raspberry Pi Turbo Mode is a hardware overclocking.
So, I worry about proper working of SD-card controller. It is possible
that the reason of the issue can be not proper controller functioning or
concrete SD-card issue.
Could you try to reproduce the issue with using another SD-card in Turbo
and normal mode?
I think that first of all it needs to detect that it is NILFS2 issue but
not hardware or MMC stack issue.
With the best regards,
Vyacheslav Dubeyko.
> maszyn ~ # mount.nilfs2 /dev/sdf3 /tmp/rpi
> mount.nilfs2: Error while mounting /dev/sdf3 on /tmp/rpi: Invalid
> argument
>
> dmesg shows:
> (...)
> [43893.754525] segctord starting. Construction interval = 300 seconds,
> CP frequency < 30 seconds
> [43893.760245] NILFS: corrupt root inode.
>
> Where should I go from here? I can hook it up via HDMI to some screen to
> see if there's some error msg on rPi.
>
> I'm using official Raspberry Pi linux 3.2.27 from github [1] (last
> updated 2-4 days ago).
>
> [1] https://github.com/raspberrypi/linux
>
>
> 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
next prev parent reply other threads:[~2012-10-09 7:29 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 [this message]
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
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=1349767793.3427.7.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;
as well as URLs for NNTP newsgroup(s).