[nSLUG] cifs on Redhat Linux, and getting a full Redhat kernel for RHEL 5

Rich budman85 at eastlink.ca
Tue May 13 13:37:34 ADT 2008


Thanks - that would be good to know.

I saw other forums talking about this as well - so you are not alone. :)

One mention about Linux extensions being enabled by default.

sbin/modprobe cifs
echo 0 > /proc/fs/cifs/LinuxExtensionsEnabled

Is this enabled?
It seems to have helped some people with smaller file access (under 2MB)




D G Teed wrote:
> The kernel compiled with smbfs support, together with a samba compiled
> from source
> to provide smbmount support have shown that the problems go away
> if smbfs is used rather than cifs.  This is true of both Linux <-> Linux
> and Linux <-> Windows mounts and access of web files over those mounts.
> With smbfs there is no file truncation when viewing html, pdf and
> multimedia files over Linux's apache.
>
> The problem has been seen in Redhat's kernels  2.6.18-53.1.13.el5
> and 2.6.18-53.1.19.  Samba is 3.0.25b-1.el5_1.4 on production server
> and I compiled 3.0.28a on a test server were I've reproduced the problem.
>
> I'm about to reproduce the problem on a third machine where we have
> Redhat support and I'm going to get them to look at this.  After all,
> this is their
> Frankenstein kernel.
>
> I'll follow up here with the results - probably a few days...
>
> --Donald
>
> On Mon, May 12, 2008 at 10:32 PM, Rich <budman85 at eastlink.ca> wrote:
>   
>>
>>
>> I know - I still prefer the tarball. :)
>>
>> I did a quick search on cifs -
>>
>> Do you mean the 255 byte limit for filenames?   If so, this might be UTF-8
>> related.
>>
>> What kernel version are you using?
>>
>>
>> The modules for 2.6.15-3 access the longer names fine.
>>
>>
>>
>>
>>
>> Rich
>>
>>
>>
>>
>>  D G Teed wrote:
>>  Thanks for the tips.
>>
>> In RHEL 4, there is a command mentioned in this KB item:
>> http://kbase.redhat.com/faq/FAQ_85_5109.shtm ....
>> up2date --get-source kernel
>>
>> yum has no equivalent and search doesn't show anything better.
>>
>> I think it was the rpmbuild step that had me perplexed. It doesn't
>> download anything, but it pulls together a bunch of files from Redhat's
>> strange source tree.
>>
>> It is a weird way to end up with kernel sources you can compile.
>> I don't know what was wrong with the old tarball way.
>>
>> This article helped me steer:
>> http://www.redhatmagazine.com/2007/11/29/tip-from-rhces-cows-in-the-linux-kernel/
>>
>> Contains a link to an FTP Redhat site for RHEL 5.
>>
>> My kernel compile is finally rolling along. I know smbfs is depreciated,
>> but I want to test and see if it is different to debug the problem.
>>
>> --Donald
>>
>> On Mon, May 12, 2008 at 6:48 PM, Rich <budman85 at eastlink.ca> wrote:
>>
>>
>>
>>  Rich wrote:
>>
>>
>>
>>  for Redhat 4 says you can get a full kernel with a special up2date
>> command. 'up2date' is not available in Redhat 5, and I don't find another
>> knowledgebase item describing how to get Redhat 5's full kernel.
>>
>>
>>
>>  Look at 'yum'
>>
>>  RH5: yum update
>>  RH4: up2date -u
>>
>>
>>  Also,
>>
>>  http://www.cyberciti.biz/faq/linux-kernel-upgrade-howto/
>>
>>
>>  One more - this one may help a lot more - shows how to use the yum
>> installer to install source kernels
>>  and other items.
>>
>>  http://www.mjmwired.net/resources/mjm-fedora-fc5.html
>>
>>
>>
>>  Rich
>>
>>
>> _______________________________________________
>>  nSLUG mailing list
>>  nSLUG at nslug.ns.ca
>>  http://nslug.ns.ca/cgi-bin/mailman/listinfo/nslug
>>
>>
>>
>>  _______________________________________________
>> nSLUG mailing list
>> nSLUG at nslug.ns.ca
>> http://nslug.ns.ca/cgi-bin/mailman/listinfo/nslug
>>
>>
>>
>> _______________________________________________
>>  nSLUG mailing list
>>  nSLUG at nslug.ns.ca
>>  http://nslug.ns.ca/cgi-bin/mailman/listinfo/nslug
>>
>>
>>     
> _______________________________________________
> nSLUG mailing list
> nSLUG at nslug.ns.ca
> http://nslug.ns.ca/cgi-bin/mailman/listinfo/nslug
>
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nslug.ns.ca/mailman/private/nslug/attachments/20080513/1b7940b5/attachment-0001.html>


More information about the nSLUG mailing list