From: Konstantinos Skarlatos <k.skarlatos@gmail.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-cifs@vger.kernel.org
Subject: Re: cifs: ls of mount point gives input/output error (probably related to CIFS: getdents() broken for large dirs)
Date: Fri, 30 Dec 2011 11:04:59 +0200 [thread overview]
Message-ID: <4EFD7EBB.2060708@gmail.com> (raw)
In-Reply-To: <4EFC7124.3060900@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1854 bytes --]
On 29/12/2011 3:54 μμ, Konstantinos Skarlatos wrote:
> On Πέμπτη, 29 Δεκέμβριος 2011 3:39:30 μμ, Jeff Layton wrote:
>> On Thu, 29 Dec 2011 12:30:18 +0200
>> Konstantinos Skarlatos<k.skarlatos@gmail.com> wrote:
>>
>>> On 29/12/2011 4:04 πμ, Jeff Layton wrote:
>>>> On Thu, 29 Dec 2011 02:08:57 +0200
>>>> Konstantinos Skarlatos<k.skarlatos@gmail.com> wrote:
>>>>
>>>>> I mount via cifs a windows XP share, df gives me correct sizes,
>>>>> but when
>>>>> I ls the mount point i get input/output error.
>>>>> strace: http://pastebin.com/WXf8M1nu
>>>>>
>>>>> mount --verbose -t cifs -o username=administrator,password=blahblah
>>>>> //192.168.0.11/jobs /mnt/backups/montaz/jobs
>>>>> mount.cifs kernel mount options:
>>>>> ip=192.168.0.11,unc=\\192.168.0.11\jobs,,ver=1,user=administrator,pass=********
>>>>>
>>>>>
>>>>> df
>>>>> //192.168.0.11/jobs 114464
>>>>> 105196 9268 92% /mnt/backups/montaz/jobs
>>>>>
>>>>> ls /mnt/backups/montaz/jobs/
>>>>> ls: reading directory /mnt/backups/montaz/jobs/: Input/output error
>>>>> total 0
>>>>>
>>>>> the fun thing is that i can cd to a lower level directory, and ls
>>>>> works
>>>>> fine there! only the mount point has the problem
>>>>>
>>>>> ls /mnt/backups/montaz/jobs/test
>>>>> total 44K
>>>>> drwxr-xr-x 1 root root 0 Apr 30 2010 blah blah/
>>>>> ......
>>>>>
>>>>> kernel version 3.2rc7
>>>>>
>>>>> this seems to be related to :
>>>>> https://lkml.org/lkml/2011/8/1/427
>>>>> Re: [3.0.0+][Regression][Bisected] CIFS: getdents() broken for
>>>>> large dirs
>>>>>
>>>> Hmmm, maybe. What makes you think that it's related? What sort of
>>>> server are you seeing this against?
>>> Windows XP service pack 2 (greek)
>>
>>
>> How many files are in the directory?
>>
> 140 folders and 20 files
>
Attached is a tcp dump of my session.
[-- Attachment #2: cifs-traffic.zip --]
[-- Type: application/octet-stream, Size: 9900 bytes --]
next prev parent reply other threads:[~2011-12-30 9:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 0:08 cifs: ls of mount point gives input/output error (probably related to CIFS: getdents() broken for large dirs) Konstantinos Skarlatos
2011-12-29 2:04 ` Jeff Layton
2011-12-29 10:30 ` Konstantinos Skarlatos
2011-12-29 13:39 ` Jeff Layton
2011-12-29 13:54 ` Konstantinos Skarlatos
2011-12-30 9:04 ` Konstantinos Skarlatos [this message]
2011-12-30 13:11 ` Jeff Layton
2011-12-30 18:00 ` Konstantinos Skarlatos
2011-12-30 21:46 ` Konstantinos Skarlatos
2011-12-31 2:16 ` Konstantinos Skarlatos
2011-12-31 11:59 ` Jeff Layton
2011-12-31 12:49 ` Konstantinos Skarlatos
2011-12-31 13:41 ` Konstantinos Skarlatos
2012-01-01 1:23 ` Jeff Layton
2012-01-01 11:44 ` Jeff Layton
2012-01-01 12:38 ` Konstantinos Skarlatos
2012-01-01 13:58 ` Konstantinos Skarlatos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EFD7EBB.2060708@gmail.com \
--to=k.skarlatos@gmail.com \
--cc=jlayton@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox