Your message dated Fri, 20 Jun 2008 17:10:36 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Kernel from Debian 3.1 no longer supported
has caused the Debian Bug report #289690,
regarding cannot access some files with samba
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
289690: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=289690
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: kernel-image-2.6.8-1-686
Version: 2.6.8-10

Dear Package Maintener,

I am using Sarge, I have just did an apt-get dist-upgrade. My previous kernel was already 2.6.8 but it was also upgraded during the dist-upgrade. I use pam_mount to mount NT server shares. It used to be working fine before the dist-upgrade, but now when I try to reach certain files (I tend to suspect that this is file size related) the command e.g. a cp just hangs then gives this:
 cp ~/local/M/data/Docs/Form.doc ./
 cp: reading `/home/tibor/local/M/data/Docs/Form.doc': Input/output error

At the same time I see this in /var/log/syslog:
Jan 10 15:35:05 matrix kernel: smb_proc_readX_data: offset is larger than SMB_READX_MAX_PAD or negative!
 Jan 10 15:35:05 matrix kernel: smb_proc_readX_data: -59 > 64 || -59 < 0
Jan 10 15:35:35 matrix kernel: smb_add_request: request [d5509e60, mid=211] timed out!


The content of ~/.pam_mount.conf is the following:
volume user01 smb ebpsfile04 tradva01$ /home/tibor/local/M uid=tibor,gid=tibor - - volume user01 smb ebpsgrpclust groups /home/tibor/local/S uid=tibor,gid=tibor - - volume user01 smb ebpsduplo IT /home/tibor/local/F uid=tibor,gid=tibor - - volume user01 smb 10.10.1.15 movies /home/tibor/local/movies uid=tibor,gid=tibor - -


The relvant (not comment) lines /etc/security/pam_mount.conf
debug 0
mkmountpoint 1
fsckloop /dev/loop7
luserconf .pam_mount.conf
options_allow   uid,gid,nosuid,nodev,loop,encryption
options_require uid,gid
lsof /usr/sbin/lsof %(MNTPT)
fsck /sbin/fsck -p %(FSCKLOOP)
losetup /sbin/losetup -p0 "%(before=\"-e \" CIPHER)" "%(before=\"-k \" KEYBITS)" %(FSCKLOOP) %(VOLUME)
unlosetup /sbin/losetup -d %(FSCKLOOP)
cifsmount /bin/mount -t cifs //%(SERVER)/%(VOLUME) %(MNTPT) -o "username=%(USER)%(before=\",\" OPTIONS)" smbmount /usr/bin/smbmount //%(SERVER)/%(VOLUME) %(MNTPT) -o "username=%(USER)%(before=\",\" OPTIONS)" ncpmount /usr/bin/ncpmount %(SERVER)/%(USER) %(MNTPT) -o "pass-fd=0,volume=%(VOLUME)%(before=\",\" OPTIONS)"
smbumount /usr/bin/smbumount %(MNTPT)
ncpumount /usr/bin/ncpumount %(MNTPT)
umount   /bin/umount %(MNTPT)
lclmount /bin/mount -p0 %(VOLUME) %(MNTPT) "%(before=\"-o \" OPTIONS)"
cryptmount /bin/mount -t crypt "%(before=\"-o \" OPTIONS)" %(VOLUME) %(MNTPT)
nfsmount /bin/mount %(SERVER):%(VOLUME) "%(MNTPT)%(before=\"-o \" OPTIONS)"
mntagain /bin/mount --bind %(PREVMNTPT) %(MNTPT)
pmvarrun /usr/sbin/pmvarrun -u %(USER) -d -o %(OPERATION)


The libc6 version I am using: 2.3.2.ds1-20


uname -a prints:
Linux matrix 2.6.8-1-686 #1 Thu Nov 25 04:34:30 UTC 2004 i686 GNU/Linux


I found the following post that may be useful:
http://lwn.net/Articles/112514/?format=printable


Regards,
Tibor


--- End Message ---
--- Begin Message ---
Version: 2.6.8-99+rm

You reported a bug against the Linux kernel (version 2.6.8) that was
shipped with Debian 3.1 (sarge).  Since Debian 3.1 is no longer
supported and the kernel has changed so much that it would be very
difficult to verify every outstanding bug from 2.6.8, I'm hereby
closing your bug report.

If you still see this issue with the kernel from the upcoming release
of Debian (lenny, version 5.0), then please me know and I'll be happy
to reopen this bug report.

Thanks.

-- 
Martin Michlmayr
http://www.cyrius.com/


--- End Message ---

Reply via email to