hardlink unlink-before-save?
in [Samba]
|
Prev: Samba Transfer Efficiency (undocumented perf hint for Win7 gives 10X write speeds)
Next: [Samba] 'rights' usage of 'Domain Admins' - User can't take possession of file on server...should it work?
From: Linda W on 21 Jun 2010 01:20 Bartosz Stec wrote: > Hello list > > On my server almost half of files are duplicated, and there are almost > 100GB of data which is growing fast. I'm using weekly script to find > duplicated files and replace them with hardlinks. Everything is fine as > long as users aren't trying to edit and save some documents which have > hardlinks. With samba 3.3 it seems that hardlinks aren't unlinked before > file is saved. > Is there any way to force samba to unlink file before write? --- Wouldn't that be a function of the application program? Some applications do similar to that -- like a rename & create (where the old file will be around as a backup). But some applications may try to modify the file in-place. It depends on the application. You might be able to force the issue by changing the permissions/ownership on the linux server to a '3rd party' login and set other permissions to read-only. Then anyone who wants to write would have to delete the copy that is there (or rename it). -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
From: Bartosz Stec on 21 Jun 2010 10:10
On 2010-06-21 07:15, Linda W wrote: > Bartosz Stec wrote: >> Hello list >> >> On my server almost half of files are duplicated, and there are >> almost 100GB of data which is growing fast. I'm using weekly script >> to find duplicated files and replace them with hardlinks. Everything >> is fine as long as users aren't trying to edit and save some >> documents which have hardlinks. With samba 3.3 it seems that >> hardlinks aren't unlinked before file is saved. >> Is there any way to force samba to unlink file before write? > --- > > Wouldn't that be a function of the application program? > > Some applications do similar to that -- like a rename & create (where > the old file will be around as a backup). But some applications may try > to modify the file in-place. It depends on the application. > > You might be able to force the issue by changing the > permissions/ownership on the linux server to a '3rd party' login and > set other permissions to read-only. Then anyone who wants to write > would have to delete the copy that is there (or rename it). I think you'r missing a point. Windows apps don't realise there is even such thing like hard link. For instance someone simply open MS Excel spreasheet, edit and save it on network share. This xls file could have one or more hardlink, but it is now ignored at all. SAMBA is in fact a layer between Unix filesystem and Windows clients and programs, so the way which I/O operations and checks on filesystem is performed are strictly samba related AFAIK. Older versions seems to behave like I want it to according to: http://lists-archives.org/samba/53311-smbd-not-breaking-hard-links-when-saving-files.html http://groups.google.com/group/mailing.unix.samba/browse_thread/thread/8a593099a36f43eb Unfortunately there was no straight answer, so I started another thread :) -- Bartosz Stec -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba |