I'll do my best, but I just don't have enough time right now for everything I have to do at home and dig this bug. I may be able to look at it in the next couple of days though, or it may go somewhere next week... That being said, I tried yesterday to have a better idea and I thank you for the "ScrLck" trick, I didn't know that it was working. Nevertheless I didn't find anything.
It seems as if the transition from the temporary kernel's fs to the hard disk's fs is not done correctly. If I boot with a working kernel after that, I can't find any trace of where it was trying to copy the files or of any partition being full. Could it be filling the RAM until it reaches its maximum capacity (16GB to fill before hitting the limit and throwing the errors)? That would explain at least why it takes so much time before the flood of errors begins... On Wed, Mar 26, 2014 at 9:18 AM, Tejun Heo <t...@kernel.org> wrote: > On Tue, Mar 25, 2014 at 09:03:51PM -0400, Alexandre Demers wrote: >> So, I tried RC8 and I'm still getting the error. It start too fast >> to be able to read whatever it is saying, but here is what I can >> read: >> ... >> cp: error writing /run/initramfs/new_root/... >> cp: failed to extend ... >> ... (and so on) >> >> It goes on like that for a long time. > > Ooh, I thought you were gonna find out what filled up the filesystem > after rebooting into the older kernel. Can you please do that? Also, > pressing "ScrLk" should stop the screen from scrolling. > > Thanks. > > -- > tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
