From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754733Ab1L2CC1 (ORCPT ); Wed, 28 Dec 2011 21:02:27 -0500 Received: from mx1.redhat.com ([209.132.183.28]:55334 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754688Ab1L2CCY (ORCPT ); Wed, 28 Dec 2011 21:02:24 -0500 Date: Wed, 28 Dec 2011 21:04:20 -0500 From: Jeff Layton To: Konstantinos Skarlatos 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) Message-ID: <20111228210420.2a422d11@corrin.poochiereds.net> In-Reply-To: <4EFBAF99.3010208@gmail.com> References: <4EFBAF99.3010208@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 29 Dec 2011 02:08:57 +0200 Konstantinos Skarlatos 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? What would be most helpful is a capture and/or some cifsFYI info. Instructions on how to capture that are here: http://wiki.samba.org/index.php/LinuxCIFS_troubleshooting Would you be able to provide those? Thanks, -- Jeff Layton