topic Re: smbmount destroys metadata in Alfresco Archive

smbmount destroys metadata

simon — Fri, 25 Jan 2008 15:36:55 GMT

Alf,We have a space with versioning applied. Add an HTML document and edit it a few times so that we have a couple versions of this file. No problems so far.Now, open this file with smbmount on UNIX and edit it with vi. Save the file and check the properties in Alfresco, everything is gone: no more

Re: smbmount destroys metadata

simon — Thu, 31 Jan 2008 08:38:52 GMT

*bump*

Re: smbmount destroys metadata

wabson — Thu, 31 Jan 2008 12:14:43 GMT

Hi Simon,

This sounds like the same problem which can occur when Alfresco is mounted using GNOME-VFS or Mac OS. The issue here is that the OS doesn't simply update the existing file upon a save, but instead creates a new file and deletes the old one.

You can check if this is what is happening with vi by looking in your Deleted Items list via your user preferences in the Alfresco Web Client - you should see all the old versions of the file there.

If this is the case then Alfresco is actually doing the correct thing as it has no way of knowing that the metadata should be copied over onto the new node. Getting round it would require some additional logic, or possibly reconfiguring vi.

Thanks,
Will.

Re: smbmount destroys metadata

loftux — Thu, 31 Jan 2008 12:18:35 GMT

That is most likely because vi doesn't open the file with a file lock. It opens the file and then creates a completely new file as the working copy. When saving and closing, it is this new file that is kept, and the original is deleted.
So for Alfresco this is a completely new file.

Other applications like MS Word is actually keeping a file lock, and when you are saving and closing, the edits are merged into the original file.

So in order to use vi, try to do a checkout. There still may be a problem as you will loose the association between the original and working copy because of the behavior above.

Peter LÃƒÂ¶fgren

Re: smbmount destroys metadata

simon — Thu, 31 Jan 2008 14:08:00 GMT

Indeed, as vi is open you see a .filename.swp file and even a file with a number as name during saving. It's also impossible to get the md5 checksum from the file after you saved it with vi.

Yes, it's vi related and I understand it's not easy for Alfresco to solve this but it's the Alfresco "filesystem" or repository that's partly the cause of this. If you do this on a UNIX filesystem this isn't a problem so it's a little easy to say it's vi's "fault", it's the combination of both.

So, it would be nice if Alfresco could solve this, or if there is way to prevent programs that destroy these files in some way. People use vi, they don't know it destroys the metadata and without knowing everything is gone… forever. Any idea how to prevent this?

Having a file repository that is interface independent is one of Alfresco strongest points but I have the feeling these interfaces are not always as equal as I would like them to be.

Re: smbmount destroys metadata

rdanner — Fri, 01 Feb 2008 03:27:14 GMT

Indeed, as vi is open you see a .filename.swp file and even a file with a number as name during saving. It's also impossible to get the md5 checksum from the file after you saved it with vi.

Yes, it's vi related and I understand it's not easy for Alfresco to solve this but it's the Alfresco "filesystem" or repository that's partly the cause of this. If you do this on a UNIX filesystem this isn't a problem so it's a little easy to say it's vi's "fault", it's the combination of both.

So, it would be nice if Alfresco could solve this, or if there is way to prevent programs that destroy these files in some way. People use vi, they don't know it destroys the metadata and without knowing everything is gone… forever. Any idea how to prevent this?

Having a file repository that is interface independent is one of Alfresco strongest points but I have the feeling these interfaces are not always as equal as I would like them to be.

It's an interesting thought. If there was to be a repository response to this it would have to be a setting – VI does what it does. Alfresco CIFS is a projection of the REPO that is meant to act like a file system. Consider that it is also annoying when you copy a folder from alfresco that you get the executables along with your copy…

I can see the desire for both behaviors – act like a file system – or act like a repo and control this darn artifact – your not a dumb file system, that's the point.

The same can be said for handling the annoying metadata files from MSWindows and mac os (.DS_Store) Can I tell alfresco to ignore these things.. send them to dev/null? I'd like to see a setting.

It's open source, we're free to fix it if we wish Maybe Gary can chime in here and give us some advice.

Re: smbmount destroys metadata

simon — Wed, 13 Feb 2008 10:10:07 GMT

Alfresco, any comment on this? Is this something your guys would like to solve in the future or should I try to ban vi out of the company?

Re: smbmount destroys metadata

simon — Wed, 27 Feb 2008 08:51:16 GMT

Answer from Alfresco:

Our assumption is that Vi works by creating a temp file for the new edits, then renames it on save. We do deal with this scenario for other applications, so it may be possible to put the same behaviour for Vi. This has to be explicitly programmed for each application. This is the first time that Vi has been requested.

Re: smbmount destroys metadata

simon — Mon, 21 Apr 2008 08:12:25 GMT

Same problem for gedit…

Re: smbmount destroys metadata

gary_spencer — Wed, 11 Jun 2008 09:43:18 GMT

There is code in the Alfresco filesystem to handle MS Word files as it does a rename shuffle to get the new version of the file in place. This was deliberately coded so it only worked with MS Word files to avoid any side effects with other file save patterns.

The problem is coming up with a generic solution that does not cause side effects. I need to do some more research on this with vi and other editors, not sure when I will get around to that with the current work load.

Gary

Re: smbmount destroys metadata

xerox — Wed, 11 Jun 2008 09:50:21 GMT

Garry,

thanks for you answer.

I think this problem needs enough prioritization.
Unexpected loss of metadata, versions for a document management system(even without a warning of the loss) is unacceptable.

Friendly regards,

Nick