Hmmm ... I'd have a look at your network card first - I've seen those
delayed write errors caused by the network giving out in some form or
another during the file transfer. In one case I had a very similar
problem caused by a power dip that happened whilst a workstation was
writing to the share. I've also had them when a flaky network card
was being used in a server.
Next time it happens, do a ps aux (or whatever the equivalent is on
your platform), and see if any of your processes are in the "D" state
(uninterruptable sleep) - if so, then that's why you have to reboot
to get access to the folder again.
Also you may want to try using ssh or ftp or somesuch to see how the
transfer speeds to your machine work (ie, test how it works without
samba). I'd recommend small and large files for the test.
On 10/12/2006, at 6:00 AM, Will Constable wrote:
I have a network server running FC5, with a hardware raid 3 card
using 5
drives, as one large (1.2TB) partition in JFS. I chose JFS because
of a
recommendation for performance from a MythTV tutorial, but I don't
really
know much about file systems and am suspecting JFS to be causing my
problems. I run samba, apache and MythTV on this machine, and
there is
essentially only one problem as far as I know.
If I write to my server from the network (only tested from windows
XP pc's
using samba), I often get either an error in windows (Delayed Write
Failed),
or windows freezes while writing. On the server side, I generally get
kernel messages from JFS that are completely meaningless to me,
just a bunch
of cryptic numbers and function calls. After one of these
problems, I can't
access the directory that was being written to, or my prompt freezes.
Rebooting seems to be the only fix- jfs does some replaying and
then the
filesystem is perfect again. This sounds a lot like a cut and dry
problem
with JFS. except that MythTV does quite a lot of high intensity
writing to
the array and never has trouble like this, yet it happens
frequently when
being written to from samba.
First of all, is there any known problem with using JFS with
samba? Aside
from that, I sort of figure maybe there is a samba configuration
option that
is to blame. Possibly something to do with buffering or with maximum
throughput allowed. I am just guessing, but can anyone help?
Thanks a lot!
Will
[EMAIL PROTECTED]
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
--
Matt Skerritt
[EMAIL PROTECTED]
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
