Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] lvm snapshot cloning



Bill Bogstad wrote:
>> ...you should consider using inotify[1].
> 
> I'm not sure how inotify would help that much. Mark...wants to
> replicate/backup only the blocks that have changed due to the files'
> large sizes.

You are correct. I was mistakenly thinking that inodes==blocks, which of
course they don't.

I haven't looked at the inotify library in a while, but it isn't out of
the realm of possibility that in addition to the notification messages
 identifying the inode, it may also identify the blocks or byte range
impacted by the I/O operation.

 -Tom


-- 
Tom Metro
Venture Logic, Newton, MA, USA
"Enterprise solutions through open source."
Professional Profile: http://tmetro.venturelogic.com/



BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org