From: Heinz Diehl <htd+ml-iEI8Y0CNJBYdnm+yROfE0A@public.gmane.org>
To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Where is nilfs2 fsck
Date: Mon, 8 Feb 2016 22:53:28 +0100 [thread overview]
Message-ID: <20160208215328.GA7586@fritha.org> (raw)
In-Reply-To: <20160208135344.09a64c7e@ulgy_thing>
On 08.02.2016, David Niklas wrote:
> Alas, my beautiful fs has become damaged and fsck does nothing, I think
> it's a nop.
> What is wrong, something in the btree, the original message was in
> syslog but it seems to have rotated, I could tell you but I'd have to
> cause my kernel to remount my home dir RO, which is not acceptable at
> this time.
> I'm not interested in the files that can't be accessed, I was trying to
> delete them when I found the error so even an experimental fsck would do.
> I do have nilfs2-utils installed but I can't find anything useful in
> there.
> Do I need to backup and reformat the partition?
There is no fsck.nilfs or similar, so yes. Nilfs2 automatically recovers most
of the time, though, so there may be underlying hardware failure. I've
been using it extensively in the last 2 years, and never seen a single
fs damage which didn't get recovered immediately.
--
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:[~2016-02-08 21:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20160208135344.09a64c7e@ulgy_thing>]
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=20160208215328.GA7586@fritha.org \
--to=htd+ml-iei8y0cnjbydnm+yrofe0a@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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).