Subject: Re: Serious Problems
From: Michael Paesold (paesold@sein.at)
Date: Wed Jun 07 2000 - 08:58:17 EDT
Dejan Muhamedagic <dejanm@aon.at> wrote:
> > The backup is done on the server, so the backuped files are corrupted,
> > too. The only solution is to open the files with the app and save them
> > to a new file. This thing mostly happens with qxp.
>
> If I got it right, qxp can open the file from the shared volume,
> but, if you copy it to the mac then it's unusable. And if you
> open it with the qxp and do "Save as" to a local disk then it's
> ok. Right? This is a long shot, but could it be that there has
> been an end-of-line translation performed during the copy
> operation? Did you try to compare the good file with the
> corrupted one? Does copy "corrupt" all files?
No, it doesn't corrupt all files nor does it corrupt the files all the time,
so this ist really strange. The end-of-line translation could be the
problem.
I think samba doesn't do that at all. And I think this is the best way. I
find it ridiculous, that a file service should be made to _actively_change_
data that it transmits. Of course, sometimes this is quite fine, but there
are too many error sources.
When I recompile netatalk I will try to deactivate -CRLF translation
completely.
> > Last night I restarted netatalk services, and the macs where
> > shutdown/restarted.
> > I tried to change permissions and to touch the file from shell (also the
> > corresponding .AppleDouble/* files). No result.
> >
> > >From <http://til.info.apple.com/techinfo.nsf/artnum/n9805>:
> > -39 eofErr End of file; no additional data in the format
>
> So, no application has been running on Mac and still Copy
> produced this error? That is strange. I have to say that I can't
> think of anything in specific. Did you check the network for
> errors (ifconfig, counters on the switch if you're using one)?
> Does this error occur regardless of the transport used (tcp or ddp)?
The strange thing is, that it only happens with some files, but I have
not been able to produce such damaged files intentionally.
> > > The Trash application needs some fiddling in order to get it to
> > > work. It also depends on the netatalk's version. However, I'd
> > > suggest that your users stay away from it, if possible.
> >
> > But how to delete files?
>
> oops :) It depends on the netatalk version. With 2.1.4-3x the
> trash won't work and users will get a warning that their files
> will be deleted for good. With 2.1.3 the situation is different
> and there has been at a time a lengthy explanation how to set up
> the trash. IIRC, it was something like creating Trash Can
> directories for all known users in advance. Check the archive on
> this. On another hand, perhaps setting restrictive permissions on
> the "Network Trash Folder" may stop users from using it. I have
> no experience with 2.1.3 so I can't give more advice here.
Since I am using 2.1.3 the trash can worked from the beginning,
but Thomas Riewe sent me advice how to deactivate the trash can
by making it unwriteable.
The hole thing with netatalk is really bad. Unlike samba, there is
only bad documentation and the hole thing is stuck in beta. I myself
have little to no experience in unix programming (especially networking)
but if the project is going to be revived, I am going to help
writing good docs for it.
Greetings,
Michael
-- Michael Paesold mailto:paesold@sein.at Vienna, Austria
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:30:58 EST