I’m performing the ls command from an ssh sessions from another linux computer. The MTU was 1500 and I changed it to 1300 but the problem persists.
From: [email protected] [mailto:[email protected]] On Behalf Of shimi Sent: Wednesday, May 02, 2012 8:05 AM To: Camelia Botez Subject: Fwd: help with ls command Hi Camelia - did you notice the mail below? I did not see a reply from you regarding that... ---------- Forwarded message ---------- From: shimi <[email protected]<mailto:[email protected]>> Date: Tue, May 1, 2012 at 2:33 PM Subject: Re: help with ls command To: Camelia Botez <[email protected]<mailto:[email protected]>> Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> On Tue, May 1, 2012 at 2:30 PM, Camelia Botez <[email protected]<mailto:[email protected]>> wrote: I’m talkibg about /usr/local/src that is on /dev/sda2 under / and indeed it is the partition I ran fsck. In other directories ls works fine. Yes the shell does manage to read the directory contents , but in one subdirectory containing no more than 24 files ls –ltr gets stuck. No the ls command is not in D state (if I’m not mistaking its state is S). Follow up question, then: Are you performing those operations over network? (and especially - over VPN/WAN/Tunnel)? If so, what you're describing sounds like the output packet sizes may be too large for your path's MTU. If you take the network interface you're coming through MTU and reduce it, to, let's say, 1300, does the problem persist? (/sbin/ifconfig eth0 mtu 1300) -- Shimi
_______________________________________________ Linux-il mailing list [email protected] http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
