In fact, hard links are not supposed to work but cp --reflink *should* work but it does not seem to. cp --reflink is what you would need to achieve what you want. Envoyé de mon appareil mobile. Jérôme Poulin Solutions G.A. On 2011-02-27, at 08:20, dexen deVries <dexen.devries@xxxxxxxxx> wrote: > Hello, > > > The following is more of a feature request than problem report, actually. > > I've mounted an older snapshot and tried to restore (add it to the current > filesystem state) by creating a hardlink. > Roughly like: > mount /dev/sdb3 ~/current > mount.nilfs2 /dev/sdb3 ~/old -o ro,cp=1234 > cd ~/current > ln ~/old/file.bin ./restored-file.bin > > The `ln' returned `Invalid cross-device link'. > > I expected such hardlink to have semantics of re-using all the data blocks & > metadata of file.bin from snapshot as restored-file.bin, so no duplication of > data blocks happens. > > > Regards, > -- > dexen deVries > > ``One can't proceed from the informal to the formal by formal means.'' > -- > 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
