Hi, On Thu, 10 Feb 2011 23:32:01 +0100, Philippe CHATAIGNON wrote: > Le Thu, 10 Feb 2011 14:01:05 +0900 (JST), > Ryusuke Konishi <ryusuke@xxxxxxxx> a écrit : > > O.K. so, it seems like something happened at the checkpoint 15731 > > according to your information. > > > > One thing wired is that the timestamp (mtime) looks to be rewinded > > at cp15731. > > > > > File: « mnt/snap6/cut/f5_20110125_202053.ts(0).Xcl » > > > Size: 6214528000 Blocks: 18446744073697366064 IO Block: > > > 4096 fichier Device: fe00h/65024d Inode: 14 > > > Links: 0 Access: (0644/-rw-r--r--) Uid: ( 1000/philippe) Gid: > > > ( 100/ users) Access: 2011-01-24 01:30:02.260271565 +0100 > > > Modify: 2011-01-24 01:30:02.260271565 +0100 > > > Change: 2011-01-25 20:28:48.894851740 +0100 > > > > Do you have any ideas on this timestamp ? > > Hi, > I pastebin all the lscp (25600 lines) at : http://dpaste.org/U6w6 > > As you can see, there is an activity at 2011-01-24 01:30:02. > 14442 2011-01-24 01:29:56 cp - 101 11 > 14443 2011-01-24 01:30:00 cp - 925 11 > 14444 2011-01-24 01:30:07 cp - 625 11 > 14445 2011-01-25 20:20:58 cp - 320 12 > 14446 2011-01-25 20:21:05 cp - 544 12 > > philippe@micro11:~$ sudo mount -t nilfs2 -r -o cp=14443 /dev/mapper/vg11a-video mnt/snap4 > philippe@micro11:~$ sudo mount -t nilfs2 -r -o cp=14444 /dev/mapper/vg11a-video mnt/snap5 > philippe@micro11:~$ sudo mount -t nilfs2 -r -o cp=14445 /dev/mapper/vg11a-video mnt/snap6 > philippe@micro11:~$ ls -lid mnt/snap4/**/** > 12 drwxr-xr-x 2 philippe users 4096 23 janv. 22:34 mnt/snap4/capture/ > 19 -rw-r--r-- 1 philippe users 4957184000 24 janv. 01:29 mnt/snap4/capture/f2_20110123_223415.ts > 16 -rw-r--r-- 1 philippe users 8606489600 9 janv. 15:42 mnt/snap4/capture/f3_20110107_205154.ts > 14 -rw-r--r-- 1 philippe users 6213324800 24 janv. 01:30 mnt/snap4/capture/f3_20110123_223247.ts > 15 -rw-r--r-- 1 philippe users 4688870400 19 janv. 23:14 mnt/snap4/capture/f4_20110119_204007.ts > 17 -rw-r--r-- 1 philippe users 6545408000 9 janv. 15:45 mnt/snap4/capture/tf1hd_20101219_203305_schrek2.ts > 18 -rw-r--r-- 1 philippe users 4434 9 janv. 15:45 mnt/snap4/channels.conf > 13 drwxr-xr-x 2 philippe users 4096 23 janv. 22:31 mnt/snap4/cut/ > philippe@micro11:~$ ls -lid mnt/snap5/**/** > 12 drwxr-xr-x 2 philippe users 4096 23 janv. 22:34 mnt/snap5/capture/ > 19 -rw-r--r-- 1 philippe users 4958387200 24 janv. 01:30 mnt/snap5/capture/f2_20110123_223415.ts > 16 -rw-r--r-- 1 philippe users 8606489600 9 janv. 15:42 mnt/snap5/capture/f3_20110107_205154.ts > 14 -rw-r--r-- 1 philippe users 6214528000 24 janv. 01:30 mnt/snap5/capture/f3_20110123_223247.ts > 15 -rw-r--r-- 1 philippe users 4688870400 19 janv. 23:14 mnt/snap5/capture/f4_20110119_204007.ts > 17 -rw-r--r-- 1 philippe users 6545408000 9 janv. 15:45 mnt/snap5/capture/tf1hd_20101219_203305_schrek2.ts > 18 -rw-r--r-- 1 philippe users 4434 9 janv. 15:45 mnt/snap5/channels.conf > 13 drwxr-xr-x 2 philippe users 4096 23 janv. 22:31 mnt/snap5/cut/ > philippe@micro11:~$ ls -lid mnt/snap6/**/** > 12 drwxr-xr-x 2 philippe users 4096 25 janv. 20:20 mnt/snap6/capture/ > 19 -rw-r--r-- 1 philippe users 4958387200 24 janv. 01:30 mnt/snap6/capture/f2_20110123_223415.ts > 16 -rw-r--r-- 1 philippe users 8606489600 9 janv. 15:42 mnt/snap6/capture/f3_20110107_205154.ts > 14 -rw-r--r-- 1 philippe users 6214528000 24 janv. 01:30 mnt/snap6/capture/f3_20110123_223247.ts > 15 -rw-r--r-- 1 philippe users 4688870400 19 janv. 23:14 mnt/snap6/capture/f4_20110119_204007.ts > 20 -rw-r--r-- 1 philippe users 1203200 25 janv. 20:20 mnt/snap6/capture/f5_20110125_202053.ts > 17 -rw-r--r-- 1 philippe users 6545408000 9 janv. 15:45 mnt/snap6/capture/tf1hd_20101219_203305_schrek2.ts > 18 -rw-r--r-- 1 philippe users 4434 9 janv. 15:45 mnt/snap6/channels.conf > 13 drwxr-xr-x 2 philippe users 4096 23 janv. 22:31 mnt/snap6/cut/ > > Interesting file is : > 14 -rw-r--r-- 1 philippe users 6214528000 24 janv. 01:30 mnt/snap5/capture/f3_20110123_223247.ts > > It's the timestamp, the size (6214528000) and the inode (14) of the file of the cp15731. > > For your information, at 1:30 the computer shuts down with 'at' command. Another remark : 2 files were recorded > simultaneously (the other one is f2_20110123_223415.ts at inode 19). Thank you for the cooperation. Yeah, this file is exactly the file that overrode "f5_20110125_202053.ts(0).Xcl" at cp15731. I don't know why the past inode overrode the latest inode. One possible explanation is that garbage collection caused this interference, and another is interference by a snapshot mount for the checkpoint 14444. Were you mounting the snapshot cp14444 when "f5_20110125_202053.ts(0).Xcl" was destroyed at cp15731 ? If not, dummy on-memory inodes used for the garbage collection seem suspicious to me. Regards, Ryusuke Konishi -- 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
