On Wed, 2012-10-24 at 09:36 +0200, Piotr Szymaniak wrote: > On Tue, Oct 23, 2012 at 05:35:30PM +0400, Vyacheslav Dubeyko wrote: > > I think that the issue is the concrete SD-card's issue. So, if you > > simply dump out the image on another SD-card then, I hope, all will work > > fine. > > But what could be the issue with SD-card? > There are several possible reasons of the issue: 1. Volume corruption. 2. File system driver issue. 3. Hardware issue. The volume corruption is steady reproducible in the case of file system driver issue on any computer system with achieving necessary environment. The reported issue is not so because you can't mount volume on SD-card but you can mount it as image on loop device. And you have different messages in these two cases. The reported issue can be a NILFS2 file system driver issue with some probability. But, as I understand, first of all, you mounted this NILFS2 volume many times in normal mode on this SD-card. Secondly, we haven't reproduction path of the reported issue for the case of Turbo mode. So, it is impossible to talk something about possible file system driver issue without understanding of technical environment and file system operations that were a reason. The hardware issue can have more probability, from my point of view. The MMC protocol describes negotiation procedure between SD-card and SD-controller. It defines voltage, frequency and operation mode between controller and card during initialization phase. So, I think that it takes place some in-proper negotiation for the case of Turbo mode or, maybe, issue of concrete hardware realization of SD-card controller or SD-controller on board. Moreover, it is possible also situation of SD card's NAND flash wearing. As a result, writing or reading operations can be failed partially or completely sometimes. With the best regards, Vyacheslav Dubeyko. > Anyway, I did a second image, mounted it as before and it works. dmesg > shows: > [ 2740.544690] NILFS warning: broken superblock. using spare superblock (blocksize = 1024). > [ 2740.544754] NILFS warning: broken superblock. using spare superblock (blocksize = 4096). > [ 2740.544760] NILFS warning: mounting unchecked fs > [ 2740.861477] NILFS: recovery complete. > [ 2740.911019] segctord starting. Construction interval = 300 seconds, CP frequency < 30 seconds > > I will try to put the image after mount/umount back to the SD-card and > check if it works on Raspberry Pi. > > > Piotr Szymaniak. -- 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
