1287276048 Q * Piet Ping timeout: 480 seconds
1287276588 J * Piet ~Piet__@04ZAAAMF1.tor-irc.dnsbl.oftc.net
1287280528 Q * _rgl Ping timeout: 480 seconds
1287282872 Q * ensc Remote host closed the connection
1287282889 J * ensc ~irc-ensc@93.159.121.26
1287283885 Q * ensc Remote host closed the connection
1287294451 Q * niki Quit: Ex-Chat
1287296560 J * ghislain ~AQUEOS@adsl2.aqueos.com
1287297253 J * BenG ~bengreen@cpc6-aztw22-2-0-cust100.aztw.cable.virginmedia.com
1287297513 Q * BenG 
1287301530 J * rgl ~Rui@a81-84-87-57.cpe.netcabo.pt
1287302021 J * derjohn_mob ~aj@80.187.237.103
1287302247 Q * rgl Read error: Connection reset by peer
1287302844 J * BenG ~bengreen@cpc6-aztw22-2-0-cust100.aztw.cable.virginmedia.com
1287302852 Q * BenG 
1287303324 J * petzsch ~markus@p4FF47295.dip.t-dialin.net
1287304758 Q * petzsch Quit: Leaving.
1287307588 J * petzsch ~markus@p4FF46C93.dip.t-dialin.net
1287309154 N * pmenier_off pmenier
1287309383 M * ghislain hello there
1287309430 M * ghislain i wanted to know if i remove the  /vservers/.hash will it affect the guest or will the link simply magicaly work the way out
1287309466 M * ghislain i allways wondered how the hashification part can recover from silly things like this
1287309741 J * derjohn_foo ~aj@80.187.237.103
1287309741 Q * derjohn_mob Read error: Connection reset by peer
1287310770 N * Bertl_oO Bertl
1287310779 M * Bertl morning folks!
1287310807 M * Bertl ghislain: it won't affect the guests or the unification at all
1287310971 Q * derjohn_foo Ping timeout: 480 seconds
1287311587 Q * petzsch Quit: Leaving.
1287312419 M * Bertl you can consider the .hash like a guest sharing with all the other guests (from the kernel point of view)
1287312895 J * derjohn_mob ~aj@88.128.54.107
1287313394 Q * derjohn_mob Read error: No route to host
1287316036 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d
1287316168 M * ghislain bert: ok i was considering the reverse like the .hash being the REAL thing and all the other pointing to it
1287316219 M * ghislain bertl: so removing it without any magic beind would break thing aven if i was thinking that link removal will only remove on reference to the data and just that
1287316227 M * PowerKe since they're hardlinks, they're all equally real
1287316237 M * PowerKe If you remove a hardlink, you just remove a reference to the same file
1287316245 M * PowerKe only when you remove the last one it gets deleted
1287316272 M * PowerKe the .hash is just an easy way to find files with the same content since the filename in the .hash directory is the hash of the content
1287316428 M * PowerKe so if you unify the first guest it creates the .hash files by creating a hardlink with the name md5(content_original_file) (actually it also considers some file attributes)
1287316468 M * PowerKe when unifying the second guest it's easy to see if a file with the same content already exists since you can just check if md5(content_file_second_guest) exists in the .hash dir
1287316504 M * PowerKe removing the .hash directory just makes the unification process harder (because all the files have to be hashed again)
1287316567 M * Bertl precisely .. off for now ... bbl
1287316572 N * Bertl Bertl_oO
1287316771 M * ghislain PowerKe: thanks i was on that thinking too but as you know being 100% sure is etter than 99% because of the murphy's law ;)
1287316772 M * PowerKe btw, it's a good idea to run pruning on the .hash directory every now and then, because if you delete the file in all the guests, the link in the .hash directory remains so the file is not deleted from disk
1287316796 M * PowerKe so you can run somethink like: find .hash -type f -links 1 -print0 | xargs -0 rm
1287316806 M * ghislain yes running the cron job we see in the FAQ for it, i am running it
1287316808 M * PowerKe (.hash being the directory of your .hash dir)
1287316844 M * ghislain but i messed the directory so i would like to change them and restart from scatch the unification
1287316919 M * PowerKe There's maybe one thing that can mess with that: if you have a file that already has hardlinks (already was unified) then it's possible that the unification process doesn't unify it again
1287316927 M * PowerKe I'm not sure if that's a setting or not
1287316963 M * PowerKe It has to do with the COW link breaking
1287316996 M * PowerKe If you have a file in a guest that is hardlinked to other files within the same guest (because you want them to have the same content), the unification process skips the file
1287317030 M * PowerKe This means it remains hardlinked to the other ones inside the guest and doesn't get the COW bit
1287317068 M * PowerKe If you then change the file in the guest, it remains linked. If it would have the COW bit, a copy would be made at that point and the links inside the guest would break
1287317098 M * PowerKe Anyway, worst case scenario you're just losing disk space (and memory sharing)
1287317236 M * PowerKe To clarify: the unification process used to only unify files in a guest that only have 1 hardlink (because it can't easily distinguish between hardlinks within a guest or with other guests)
1287317344 M * PowerKe Unless someone changed that code, it could be that already unified files won't end up in the .hash directory again
1287317451 Q * balbir_ Ping timeout: 480 seconds
1287317472 M * PowerKe Still, it will not break anything inside the guests, you'll just have less sharing
1287317585 M * PowerKe The only thing that will mess up your guests is not enabling the extended attributes after you unified them. In that case the COW bit is gone and changing a file in one guest will change the same file in all other guests.
1287318117 J * balbir_ ~balbir@122.172.165.25
1287319020 J * derjohn_mob ~aj@88.128.169.153
1287319773 J * derjohn_foo ~aj@tmo-046-232.customers.d1-online.com
1287319974 M * ghislain ok thanks for all the explanations ! :)
1287320046 J * aj__ ~aj@88.128.58.75
1287320106 J * petzsch ~markus@tmo-101-117.customers.d1-online.com
1287320163 Q * derjohn_mob Ping timeout: 480 seconds
1287320230 J * petzsch1 ~markus@tmo-101-179.customers.d1-online.com
1287320251 J * derjohn_mob ~aj@88.128.66.0
1287320285 Q * derjohn_foo Ping timeout: 480 seconds
1287320585 Q * aj__ Ping timeout: 480 seconds
1287320591 Q * petzsch Ping timeout: 480 seconds
1287321108 Q * balbir_ Ping timeout: 480 seconds
1287321426 Q * derjohn_mob Read error: No route to host
1287322124 Q * petzsch1 Quit: Leaving.
1287326315 Q * FireEgl Quit: Leaving...
1287326717 Q * ensc|w_ Remote host closed the connection
1287326728 J * ensc|w ~ensc@www.sigma-chemnitz.de
1287327726 J * petzsch ~markus@tmo-109-226.customers.d1-online.com
1287329319 Q * petzsch Quit: Leaving.
1287330998 Q * pmenier Quit: Konversation terminated!
1287331074 J * pmenier ~pmenier@ACaen-152-1-59-141.w83-115.abo.wanadoo.fr
1287333514 J * petzsch ~markus@dslb-188-103-056-236.pools.arcor-ip.net
1287334035 J * derjohn_mob ~aj@tmo-051-90.customers.d1-online.com
1287335729 J * ghislain1 ~AQUEOS@adsl2.aqueos.com
1287335832 Q * pmenier Quit: Konversation terminated!
1287335956 Q * ghislain Ping timeout: 480 seconds
1287336233 P * kupo 
1287336292 J * derjohn_foo ~aj@80.187.232.122
1287336655 Q * derjohn_mob Ping timeout: 480 seconds
1287337947 J * ghislain ~AQUEOS@adsl2.aqueos.com
1287337981 Q * matti Remote host closed the connection
1287338193 Q * ghislain1 Ping timeout: 480 seconds
1287339298 J * derjohn_mob ~aj@tmo-033-101.customers.d1-online.com
1287339625 Q * derjohn_foo Ping timeout: 480 seconds
1287340605 J * derjohn_foo ~aj@88.128.165.10
1287340735 Q * derjohn_mob Ping timeout: 480 seconds
1287341773 J * aj__ ~aj@tmo-088-0.customers.d1-online.com
1287341986 J * derjohn_mob ~aj@88.128.137.241
1287342176 Q * derjohn_foo Ping timeout: 480 seconds
1287342264 Q * aj__ Ping timeout: 480 seconds
1287342535 Q * derjohn_mob Ping timeout: 480 seconds
1287343249 J * derjohn_mob aj@88.128.48.75
1287344305 Q * derjohn_mob Ping timeout: 480 seconds
1287344316 J * derjohn_mob ~aj@88.128.29.14
1287344737 J * derjohn_foo ~aj@88.128.206.117
1287345085 Q * derjohn_mob Ping timeout: 480 seconds
1287345173 J * ghislain1 ~AQUEOS@adsl2.aqueos.com
1287345480 Q * ghislain Ping timeout: 480 seconds
1287347316 Q * ghislain1 Quit: Leaving.
1287348683 Q * Piet Ping timeout: 480 seconds
1287348892 Q * petzsch Quit: Leaving.
1287348901 J * FireEgl ~FireEgl@2001:470:e056:8:ecc6:b666:fc4:ab71
1287349256 J * Piet ~Piet__@04ZAAAM14.tor-irc.dnsbl.oftc.net
1287349727 Q * bonbons Quit: Leaving
1287351281 Q * ntrs Ping timeout: 480 seconds
1287351284 Q * derjohn_foo Read error: Connection reset by peer
1287351792 J * ntrs ~ntrs@vault08.rosehosting.com
1287356743 J * niki ~niki@94.145.207.11