From: Paul Fertser <fercerpav-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: New experience with the odd problem starting nilfs_cleanerd due to an eMMC misbehaviour
Date: Thu, 10 Jan 2013 18:12:22 +0400 [thread overview]
Message-ID: <20130110141222.GD29689@home.lan> (raw)
In-Reply-To: <1357826459.2050.52.camel@slavad-ubuntu>
On Thu, Jan 10, 2013 at 06:00:59PM +0400, Vyacheslav Dubeyko wrote:
> Anyway, thank you for the report.
Big thanks to you for caring about the project!
> > I think you can reproduce something similar with loopback mounting if
> > you modify the driver to return read error for some particular sectors
> > that cleanerd wants to access when it starts cleaning.
>
> Yes, it is a good idea. I'll try it. But I worry only that it is
> possible to investigate not the issue that was reported by you.
I think what's important is to keep in mind the following failure
scenario: a misbehaving media suddenly starts returning read errors
consistently for a number of sectors until the whole erase block is
written to.
I also found two nice options to simulate my situation:
http://stackoverflow.com/questions/1870696/simulate-a-faulty-block-device-with-read-errors
Good luck and happy hacking.
Spasibo!
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
--
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:[~2013-01-10 14:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 13:52 Odd problem starting nilfs_cleanerd due to an eMMC misbehaviour Paul Fertser
[not found] ` <20120126135203.GM2267-0MSThuzptbI@public.gmane.org>
2012-01-27 16:19 ` Christian Smith
[not found] ` <20120127161921.GL750-Ng8wz+J301SNY5Lh21HnMTHS2PGA244I9dF7HbQ/qKg@public.gmane.org>
2012-01-27 16:29 ` Gordan Bobic
2012-01-28 12:53 ` Martin Steigerwald
[not found] ` <201201281353.00537.Martin-3kZCPVa5dk2azgQtNeiOUg@public.gmane.org>
2012-02-01 6:06 ` Paul Fertser
2013-01-10 13:16 ` New experience with the odd " Paul Fertser
[not found] ` <20130110131659.GA29689-0MSThuzptbI@public.gmane.org>
2013-01-10 13:34 ` Vyacheslav Dubeyko
2013-01-10 13:49 ` Paul Fertser
[not found] ` <20130110134907.GB29689-0MSThuzptbI@public.gmane.org>
2013-01-10 14:00 ` Vyacheslav Dubeyko
2013-01-10 14:12 ` Paul Fertser [this message]
2013-06-30 7:44 ` Paul Fertser
[not found] ` <20130630074404.GI22224-0MSThuzptbI@public.gmane.org>
2013-06-30 7:56 ` Paul Fertser
[not found] ` <20130630075626.GJ22224-0MSThuzptbI@public.gmane.org>
2013-06-30 11:49 ` Vyacheslav 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=20130110141222.GD29689@home.lan \
--to=fercerpav-re5jqeeqqe8avxtiumwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.