Subject: Re: [netatalk-admins] 1.4b2 (with Volumesize Patch) or +Asun Patch
From: Osma Ahvenlampi (oa@spray.fi)
Date: Tue May 19 1998 - 03:44:42 EDT
Patrik Schindler <poc@pocnet.net> writes:
> The first Disk is new and both are well-tested with NO defects. It's
> NOT the Disks. May anyone please try to verify my discovery on a test
> partition? I'm not programmer enough to say, what's exactly going
> wrong.
I run Netatalk 1.4b2 + asun18a2.0 on a Linux 2.0.33 kernel system in a
production environment, with MacOS 8.0 and 8.1 clients. While
performance could be better (but I attribute this to inferior Ethernet
interfaces on the Macs, since pure TCP/IP traffic on them is slow as
well), I definitely have no problems with filesystem corruption.
And while I don't have any intimate knowledge of ext2 or Linux
filesystem API (as opposed to the usermode file I/O API, which I do
know well enough) or Netatalk code (I've only looked at the
authentication code), as a programmer, I can't see how a program like
Netatalk could possibly corrupt a filesystem in the way you describe.
The log messages you see are caused by the ext2 filesystem detecting
existing corruption while processing Netatalk's I/O.
-- For a holy stint, a moth of the cloth gave up his woolens for lint. Osma Ahvenlampi <oa@spray.fi>
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:32:43 EST