On Sat, Oct 24, 2015 at 12:10:48PM +0900, Masanari Iida wrote: > > My wild guess is > file was created in inode #100 (for example), > it was deleted and inode #100 moved to orphan list. > The inode #100 was re-used in step 3. The inode is removed from the orphan list as soon as the inode is released. The only time an inode remains on the orphan list is if some other process had an open file descriptor on the file before it was unlinked. But in that case, when you recreate the file with the same name, you will get a new inode, because the old inode has not yet been released. Once it has been released, it is removed from the orphan list. > snapshot taken. If the storage device is not synchronized with the file system then there is no guarantee that the snapshot will be consistent. But given that you said you waited for hours before taking the snapshot, and it seems likely that isn't the problem. > Did we have such trouble during 2.6.32 time? I don't recall anything like that. But if you are still using 2.6.32, then presumably you are on some enterprise distro. I suggest you open a support call with your enterprise distro provider, and/or with your storage device (since I assume you're using some kind of storage array that has a proprietary device driver). Cheers, - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
