linux-nilfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
To: Paul Fertser <fercerpav-Re5JQEeQqe8AvxtiuMwx3w@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 17:34:22 +0400	[thread overview]
Message-ID: <1357824862.2050.48.camel@slavad-ubuntu> (raw)
In-Reply-To: <20130110131659.GA29689-0MSThuzptbI@public.gmane.org>

Hi,

On Thu, 2013-01-10 at 17:16 +0400, Paul Fertser wrote:
> Hi,
> 
> I've reported this issue earlier and back then it "resolved itself"
> after a power-cycle. The hardware in question is the same ac100
> netbook with an internal 32GB eMMC.
> 
> On nilfs_cleanerd start i was consistently getting these messages:
> [   46.122096] mmcblk0: error -110 transferring data, sector 26671630, nr 10, card status 0x200900
> [   48.934623] mmcblk0: error -110 transferring data, sector 26671631, nr 9, card status 0x200900
> (and similar output for two other sectors)
> 
> However, this time was different, several full power cycles didn't
> help and the read was still failing and cleanerd refused to start.
> 

Could you share system log content and strace of nilfs_cleanerd's trying
to start in the case of the issue? It needs for the beginning of the
issue understanding. Please, set in the nilfs_cleanerd.conf debug level.

Could you made raw dump of bad sectors? Could you share dumpseg output
for segments which contains the bad sectors?

So, I need to think how to investigate your issue without availability
of eMMC. :-)

Thanks,
Vyacheslav Dubeyko.

> So i resorted to brute force, trying to write to the sectors in
> question. 512 and 2048 byte writes were failing with the same error
> message, so i tried 4096 and it took about a second but succeeded:
> 
> dd if=/dev/zero of=/dev/mmcblk0 bs=4096 count=1 seek=3333953
> 
> Same has to be done with the other failing sector.
> 
> And only after that i was able to start nilfs_cleanerd and my system
> seems to be running fine again.
> 
> If it happened with e.g. ext4, i would be unable to read a certain
> file and after several attempts would simply delete it and the blocks
> in question would get overwritten eventually without any impact for
> the system usability. However, with nilfs had i not figured out the
> "dd" trick i would have to overwrite the whole filesystem (and in fact
> that's the main and only partition on my netbook). The described mmc
> card behaviour (i.e. remapping bad blocks only on write attempts)
> seems to be kind of reasonable and i would expect the same problem to
> happen with someone else one day.
> 
> HTH


--
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:[~2013-01-10 13:34 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 [this message]
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
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=1357824862.2050.48.camel@slavad-ubuntu \
    --to=slava-yeenwd64clxbdgjk7y7tuq@public.gmane.org \
    --cc=fercerpav-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).