--===============1862113680==
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="+xNpyl7Qekk2NvDX"
Content-Disposition: inline


--+xNpyl7Qekk2NvDX
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Max,
I am testing an opaque VFS module with the mount.cifs and I have run
into a similar problem. Everything seems to work, but when I run into
an issue, the kernel freezes the process and sometimes I can recover
by killing the background process (that the VFS is connecting to) but
often I cannot and the only way out is the Magic Key (SysRq-S,SysRq-U,
SysRq-B). You should really look into enabling this in your kernel.

Anyway, for me it happens usually when I copy a file larger than 8Mb
onto the share. If I stick to smaller files, everything goes smoothly.
Please let me know if you find any resolution for this problem on this
or the linux kernel or linux-cifs mailing lists.=20

I have tried both with 2.6.8 and 2.6.15 kernels with same result.

Regards,
-Jiri

PS: I tried to use smbfs, but it has a bug in chmod and every chmod
call will take 30 seconds to timeout for me, so its not much of use.
I think I have filled a bug (2828) for this one, but didn't follow
through with proper debuging info.

On Fri 30-12-05 11:13:21, Max Kipness wrote:
> I've been using the latest cifs 1.8 client at http://linux-cifs.samba.org/
> with Fedora 3 and RHE 4.
>=20
> This client seems to have a lot of issues that I did not notice when using
> smbfs. It seems like when there is an issue with connectivity to a windows
> machine, and you try to access a cifs mount, the entire session locks up.
> I basically have to kill the session, log back on, and then there is no
> way to kill the process as it is showing a 'D' for 'waiting for I/O. There
> have been times on various linux servers where I had so many unkillable
> cifs processes that I then could not even do a reboot or shutdown of the
> system. I have had to physically hold the power down to halt the computer.
>=20
> My question is whether this in any way relates to Samba itself on the
> system. I see various revisions of the whole Samba suite, but I believe
> these revisions only handle improvements on the server-end.
>=20
> Anybody else using cifs for connectivity that has had these issues? Are
> there any ways around this or it is the product just unstable at this
> point?
>=20
> Thanks,
> Max
>=20
>=20
> --=20
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/listinfo/samba


--=20
Jiri Klouda
http://www.zg.cz/~jk

--+xNpyl7Qekk2NvDX
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDzsX6pxwzMweqZNwRArdNAKCkePRL40zWBhnpokfRXK dLTIH6mwCgl9rB
rQ4jEn3EwBBj4I/KmXExnjw=
=w98N
-----END PGP SIGNATURE-----

--+xNpyl7Qekk2NvDX--

--===============1862113680==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
--===============1862113680==--