From: KARBOWSKI Piotr <piotr.karbowski-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [!] Unable to mount nilfs2 filesystem after power outage - error loading super root.
Date: Fri, 18 Mar 2016 19:16:29 +0100 [thread overview]
Message-ID: <56EC45FD.7010808@gmail.com> (raw)
Hi,
Yesterday I had an power outage. After booting my notebook again, I was
no longer able to mount /home that was on the top of nilfs2 filesystem.
I've come across a post from 2011 about fsck in git.nilfs.org but that
repo is no longer accessable. The repo from githab does not have any
trace of the experimental fsck tool thus I've dumped the filesystem to
image, recreated ext4 and restored backup.
The symptoms:
# mount -o loop ./kurogane_ssd-home.17.03.2016.img /mnt/tmp
mount.nilfs2: Error while mounting /dev/loop/0 on /mnt/tmp: No such file
or directory
# dmesg
[ 9591.626210] NILFS warning: mounting unchecked fs
[ 9591.824166] NILFS: error loading super root.
No nilfs-utils's tools works beside the tune with -l
# nilfs-tune -l /dev/loop1
nilfs-tune 2.2.2
Filesystem volume name: home
Filesystem UUID: 6a915104-61d5-4214-bed4-2538d1bdfaa5
Filesystem magic number: 0x3434
Filesystem revision #: 2.0
Filesystem features: (none)
Filesystem state: invalid or mounted
Filesystem OS type: Linux
Block size: 4096
Filesystem created: Sat Nov 14 14:40:18 2015
Last mount time: Thu Mar 17 17:41:23 2016
Last write time: Thu Mar 17 22:46:08 2016
Mount count: 154
Maximum mount count: 50
Reserve blocks uid: 0 (user root)
Reserve blocks gid: 0 (group root)
First inode: 11
Inode size: 128
DAT entry size: 32
Checkpoint size: 192
Segment usage size: 16
Number of segments: 11294
Device size: 94745133056
First data block: 1
# of blocks per segment: 2048
Reserved segments %: 5
Last checkpoint #: 1016585
Last block address: 17023836
Last sequence #: 80736
Free blocks count: 6764544
Commit interval: 0
# of blks to create seg: 0
CRC seed: 0x60cb4676
CRC check sum: 0x68371ded
CRC check data size: 0x00000118
This is something I woudn't expect from a log structured filesystem. I
am running kernel 4.5.0.
Any comments and help with restoring access to this fs much appriecieate
-- Piotr.
--
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 reply other threads:[~2016-03-18 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 18:16 KARBOWSKI Piotr [this message]
[not found] ` <56EC45FD.7010808-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-03-18 20:13 ` [!] Unable to mount nilfs2 filesystem after power outage - error loading super root Viacheslav Dubeyko
[not found] ` <1458331991.2615.6.camel-dzAnj6fV1RzTdvqWZYKEhEEK6ufn8VP3@public.gmane.org>
2016-03-18 20:40 ` KARBOWSKI Piotr
[not found] ` <56EC67A2.8050905-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-03-18 21:36 ` Viacheslav Dubeyko
[not found] ` <1458337014.2615.14.camel-dzAnj6fV1RzTdvqWZYKEhEEK6ufn8VP3@public.gmane.org>
2016-03-18 22:14 ` KARBOWSKI Piotr
[not found] ` <56EC7DCE.1020906-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-03-18 22:45 ` Viacheslav 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=56EC45FD.7010808@gmail.com \
--to=piotr.karbowski-re5jqeeqqe8avxtiumwx3w@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 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).