On Thu, 2013-08-29 at 19:47 -0400, Jérôme Poulin wrote: > On Mon, Aug 26, 2013 at 6:09 AM, Vyacheslav Dubeyko <slava@xxxxxxxxxxx> wrote: > > As I remember, one of the report is contained such error message. But I > > can't recollect in what environment such error message was. > > > > I suspect that it is a sequence of the problem that it was more earlier. > > Did you have any NILFS2 error messages in your system log earlier? Or, > > maybe, do you try to use NILFS2 volume after getting some NILFS2 issue > > earlier? > > I continued using the volume daily as the issue only popped out when > using apt-get, so I was safe for the rest. Now I migrated to ext4 to > get my laptop working, I was able to succesfully rsync all the data on > a new volume and keep the NILFS2 volume archived. > > Earlier logs: > Aug 23 22:08:50 JeromeCauca nilfs_cleanerd[2369]: start > Aug 23 22:08:50 JeromeCauca nilfs_cleanerd[2369]: pause (clean check) > First time it happened was there: > Aug 24 03:59:10 JeromeCauca nilfs_cleanerd[2369]: resume (clean check) > Aug 24 03:59:40 JeromeCauca kernel: [21196.506395] > nilfs_ioctl_move_inode_block: conflicting data buffer: ino=76070, > cno=3769693, offset=0, blocknr=46096310, vblocknr=4731085 > Aug 24 03:59:40 JeromeCauca kernel: [21196.506425] NILFS: GC failed > during preparation: cannot read source blocks: err=-17 > Aug 24 03:59:40 JeromeCauca nilfs_cleanerd[2369]: cannot clean > segments: File exists > Aug 24 03:59:40 JeromeCauca nilfs_cleanerd[2369]: shutdown > > I don't have anything earlier than August 21st and not any other log > has "nilfs" in them. Yes, I think that it needs to investigate the issue more deeply. But I haven't enough time currently for investigated several issues simultaneously. :) So, this issue will be in my TODO list. But, anyway, it needs to understand the reproducing path. Do you have any assumptions how to reproduce this situation? Thanks, Vyacheslav Dubeyko. > -- > 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 -- 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
