Re: New experience with the odd problem starting nilfs_cleanerd due to an eMMC misbehaviour

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2013-01-10 at 17:49 +0400, Paul Fertser wrote:
> Hi,
> 
> On Thu, Jan 10, 2013 at 05:34:22PM +0400, Vyacheslav Dubeyko wrote:
> > On Thu, 2013-01-10 at 17:16 +0400, Paul Fertser wrote:
> > > 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.
> 
> Eh, sorry, i was too involved in thinking about how to fix the issue
> and so haven't saved any extra logs :(
> 

Anyway, thank you for the report.

> > Could you made raw dump of bad sectors? Could you share dumpseg output
> > for segments which contains the bad sectors?
> 
> The bad sectors in question were unreadable with dd, it just hanged
> for a moment and an additional error -110 was output to dmesg.
> 
> > So, I need to think how to investigate your issue without availability
> > of eMMC. :-)
> 
> 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.

Thanks,
Vyacheslav Dubeyko.

> Sorry again for not having saved enough details.
> 


--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Filesystem Development]     [Linux BTRFS]     [Linux CIFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux