On Thu, 07 Jul 2011 12:21:42 +0900 (JST), Ryusuke Konishi wrote: > On Wed, 6 Jul 2011 19:19:37 +0200, dexen deVries wrote: > > On Wednesday 06 July 2011 18:05:29 you wrote: > > and also I'm using lilo, which is not supported by NILFS2 yet -- > > lack of fibmap syscall. > > This topic was once discussed with the title of "FIBMAP ioctl > missing". > > fibmap internally uses bmap vfs method. Adding the feature is not so > difficult, but it must not be used for overwriting data blocks because > nilfs everytime changes allocation of file blocks due to its COW > nature. Garbage collection also blows up safety of such operation. > Unfortunately, swap file is actually doing it. > > Does LILO use fibmap for read-only purpose ? > > If so, we only need a method to deny direct block write by the swap > file. That was not enough. I guess LILO uses block mapping assuming it's pinned to the place. It's not easy to implement within nilfs. 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
