Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: "Frédéric L. W. Meunier" <fredlwm-fLz7/M+a0ZzR7s880joybQ@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: CIFS shares keep hanging with VirtualBox
Date: Thu, 19 Apr 2012 16:43:57 -0300	[thread overview]
Message-ID: <20120419194357.GA4574@pervalidus> (raw)
In-Reply-To: <20120419135151.6745d624-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]

On Thu, Apr 19, 2012 at 01:51:51PM -0400, Jeff Layton wrote:
> 
> On Thu, 19 Apr 2012 14:36:27 -0300 Frédéric L. W. Meunier wrote:
> 
> > I use VirtualBox (4.1.12) on Windows 7 Ultimate SP1. The guest is Linux 
> > (kernel 3.3.2, cifs-utils 5.3), which I boot directly from a partition.
> > 
> > If I use CIFS to access the Windows partitions, the connections 
> > constantly hang and the applications to access it deadlock until killed.
> 
> Looks like the server just isn't responding to echo requests. Sniffing
> the traffic between client and server might be good to confirm that:
> 
>     https://wiki.samba.org/index.php/LinuxCIFS_troubleshooting#Wire_Captures
> 
> Are you connecting to the CIFS server in windows 7 with this? Or some
> other VMware SMB server thingy?

Yes. It's the same computer. I use VirtualBox in Windows 7 to boot 
Linux, which is installed in the same hard drive. Then, in Linux, I use 
CIFS to have access to the Windows 7 partitions.

I captured a log with 'tcpdump', but I don't think it's of any use. It 
stopped logging at 16:01 but the hang happened after that. It didn't log 
anything from the problematic 'ls', 'kill -9' and 'umount /mnt/ntfs2'.

[-- Attachment #2: cifs-traffic.pcap.gz --]
[-- Type: application/octet-stream, Size: 9636 bytes --]

  parent reply	other threads:[~2012-04-19 19:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19 17:36 CIFS shares keep hanging with VirtualBox Frédéric L. W. Meunier
     [not found] ` <20120419135151.6745d624@corrin.poochiereds.net>
     [not found]   ` <20120419135151.6745d624-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2012-04-19 19:43     ` Frédéric L. W. Meunier [this message]
2012-04-19 20:19       ` Steve French
     [not found]         ` <CAH2r5muAnRf-cNbE2WH6a1fZmX+diti+bbtCK-iju7wdKm7L8g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-19 23:39           ` Frédéric L. W. Meunier
2012-04-20  2:10             ` Steve French

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=20120419194357.GA4574@pervalidus \
    --to=fredlwm-flz7/m+a0zzr7s880joybq@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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