From: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
To: Paul Fertser <fercerpav-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Ryusuke Konishi
<konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>,
Brian Cottingham
<spiffytech-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-nilfs <linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Unrecovered read error issue
Date: Sat, 19 Dec 2015 13:58:10 -0800 [thread overview]
Message-ID: <1450562290.2693.9.camel@ubuntu-slavad-14.04> (raw)
In-Reply-To: <20151219071703.GP3706-VZXms658p7SUKArSQO4KrA@public.gmane.org>
Hi Paul,
On Sat, 2015-12-19 at 10:17 +0300, Paul Fertser wrote:
> Hey Viacheslav,
>
> On Fri, Dec 18, 2015 at 05:26:12PM -0800, Viacheslav Dubeyko wrote:
> > So, what do you think about such issue? What possible and easy solution
> > do you see? We haven't opportunity for long-term implementation and we
> > need in some easy hack for it. What do you think?
>
> I reported this issue several years ago (in my case GC was choking on
> bad sectors of an eMMC), and no hack was considered to be necessary; I
> had to resort to manually dd 4096 zero bytes to the affected block
> every time I faced it.
>
> I'm glad to see this is finally getting some attention!
>
I think that I've encounter likewise problem with Seagate hybrid HDD
too.
But I suppose that eMMC or SSD will do re-assignment of bad logical
sector into valid physical page on write operation. And I am not sure
that bad sector will be re-assigned on write operation for HDD case.
File systems had special bad sectors table a decades ago. But this table
is considered as unnecessary metadata structure in modern file systems.
So, it needs to process likewise error as for read operation as for
write operation too, I assume.
Thanks,
Vyacheslav Dubeyko.
--
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:[~2015-12-19 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-19 1:26 Unrecovered read error issue Viacheslav Dubeyko
[not found] ` <1450488372.2652.25.camel-dzAnj6fV1RzTdvqWZYKEhEEK6ufn8VP3@public.gmane.org>
2015-12-19 7:17 ` Paul Fertser
[not found] ` <20151219071703.GP3706-VZXms658p7SUKArSQO4KrA@public.gmane.org>
2015-12-19 21:58 ` Vyacheslav Dubeyko [this message]
[not found] ` <1450562290.2693.9.camel-RC04EVaD3rlUdzgqiOAiT0EK6ufn8VP3@public.gmane.org>
2015-12-20 18:34 ` Clemens Eisserer
[not found] ` <CAFvQSYTHYypic+bjUOxK=F81XgA1zOvviKkAKQuJ2fD==tn02w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-12-20 21:55 ` 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=1450562290.2693.9.camel@ubuntu-slavad-14.04 \
--to=slava-yeenwd64clxbdgjk7y7tuq@public.gmane.org \
--cc=fercerpav-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=spiffytech-Re5JQEeQqe8AvxtiuMwx3w@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).