From: mikael-m2T68/X/qvZAfugRpC6u6w@public.gmane.org
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: NILFS error after power loss
Date: Sun, 16 Jul 2017 21:37:01 +0200 [thread overview]
Message-ID: <39eaa9df1d7d61fbcbfba585f26896e5@fripost.org> (raw)
In-Reply-To: <3909a3843e9fc28c7c1f7812f47b7b2b-m2T68/X/qvZAfugRpC6u6w@public.gmane.org>
Hi,
The battery in my laptop, Lenovo X1 Carbon, with NixOS version 17.03 ran
out of power in May. When I started the laptop again, it did not boot
properly. I have used another laptop since then.
I booted it with a Live USB with NixOS 17.03 and followed the
instructions under the section 'NILFS got stuck' at
http://nilfs.sourceforge.net/en/faq.html:
# echo t > /proc/sysrq-trigger
# dmesg
I should say I have no prior experience of sysrq. Anyhow, you can see
the dmesg output at the following link:
https://mega.nz/#F!4UoFwYaQ!u7GEnZ3n0BUyNexe3vI2-w
Please get back to me if you want more information.
Not sure if this is of any interest but this is an excerpt from
journalctl:
Apr 24 06:55:22 nixos kernel: NILFS (dm-0): bad btree node (ino=1609,
blocknr=13626216): level = 51, flags = 0x44, nchildren = 12298
Apr 24 06:55:22 nixos kernel: NILFS error (device dm-0):
nilfs_bmap_lookup_contig: broken bmap (inode number=1609)
Apr 24 06:55:22 nixos kernel: Remounting filesystem read-only
Apr 24 06:55:22 nixos kernel: NILFS (dm-0): bad btree node (ino=1609,
blocknr=13626216): level = 51, flags = 0x44, nchildren = 12298
Apr 24 06:55:22 nixos kernel: NILFS error (device dm-0):
nilfs_bmap_lookup_contig: broken bmap (inode number=1609)
Apr 24 06:55:22 nixos kernel: NILFS (dm-0): bad btree node (ino=1609,
blocknr=13626216): level = 51, flags = 0x44, nchildren = 12298
Apr 24 06:55:22 nixos kernel: NILFS error (device dm-0):
nilfs_bmap_lookup_contig: broken bmap (inode number=1609)
Apr 24 06:55:22 nixos kernel: NILFS (dm-0): bad btree node (ino=1609,
blocknr=13626216): level = 51, flags = 0x44, nchildren = 12298
Apr 24 06:55:22 nixos kernel: NILFS error (device dm-0):
nilfs_bmap_lookup_contig: broken bmap (inode number=1609)
Apr 24 06:55:22 nixos kernel: NILFS (dm-0): bad btree node (ino=1609,
blocknr=13626216): level = 51, flags = 0x44, nchildren = 12298
Apr 24 06:55:22 nixos kernel: NILFS error (device dm-0):
nilfs_bmap_lookup_contig: broken bmap (inode number=1609)
Apr 24 06:55:22 nixos kernel: NILFS (dm-0): bad btree node (ino=1609,
blocknr=13626216): level = 51, flags = 0x44, nchildren = 12298
Apr 24 06:55:22 nixos kernel: NILFS error (device dm-0):
nilfs_bmap_lookup_contig: broken bmap (inode number=1609)
Apr 24 06:55:22 nixos kernel: NILFS (dm-0): bad btree node (ino=1609,
blocknr=13626216): level = 51, flags = 0x44, nchildren = 12298
Apr 24 06:55:22 nixos kernel: NILFS error (device dm-0):
nilfs_bmap_lookup_contig: broken bmap (inode number=1609)
Apr 24 06:55:22 nixos kernel: NILFS (dm-0): bad btree node (ino=1609,
blocknr=13626216): level = 51, flags = 0x44, nchildren = 12298
Apr 24 06:55:22 nixos kernel: NILFS error (device dm-0):
nilfs_bmap_lookup_contig: broken bmap (inode number=1609)
Apr 24 06:55:22 nixos kernel: NILFS (dm-0): bad btree node (ino=1609,
blocknr=13626216): level = 51, flags = 0x44, nchildren = 12298
Apr 24 06:55:22 nixos kernel: NILFS error (device dm-0):
nilfs_bmap_lookup_contig: broken bmap (inode number=1609)
Apr
Kind regards,
Mikael Andersson
--
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 parent reply other threads:[~2017-07-16 19:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3909a3843e9fc28c7c1f7812f47b7b2b@fripost.org>
[not found] ` <3909a3843e9fc28c7c1f7812f47b7b2b-m2T68/X/qvZAfugRpC6u6w@public.gmane.org>
2017-07-16 19:37 ` mikael-m2T68/X/qvZAfugRpC6u6w [this message]
[not found] ` <39eaa9df1d7d61fbcbfba585f26896e5-m2T68/X/qvZAfugRpC6u6w@public.gmane.org>
2017-07-16 22:47 ` NILFS error after power loss Peter Grandi
[not found] ` <78546a7101d18887029883c515fadbf5@fripost.org>
[not found] ` <78546a7101d18887029883c515fadbf5-m2T68/X/qvZAfugRpC6u6w@public.gmane.org>
2017-07-22 15:21 ` Peter Grandi
[not found] ` <6603e34b36ee6db3997c47e450fc28dd@fripost.org>
[not found] ` <6603e34b36ee6db3997c47e450fc28dd-m2T68/X/qvZAfugRpC6u6w@public.gmane.org>
2017-07-31 13:20 ` Peter Grandi
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=39eaa9df1d7d61fbcbfba585f26896e5@fripost.org \
--to=mikael-m2t68/x/qvzafugrpc6u6w@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