From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [gfs2][RFC] readdir caused ls process into D (uninterruptible) state, under testing with Samba 3.0.25
Date: Thu, 16 Aug 2007 09:28:48 +0100 [thread overview]
Message-ID: <1187252928.8765.881.camel@quoit> (raw)
In-Reply-To: <91b13c310708160120v7379d867k73ecf1995719d694@mail.gmail.com>
Hi,
On Thu, 2007-08-16 at 16:20 +0800, ??? wrote:
> It seems that gfs2 cannot work well with Samba,
>
> I'm using the gfs2 and the new cluster suite(cman with openais),
>
> 1. the testing environment is that 1 iscsi target and 2 cluster node,
> 2. the two nodes both used iscsi initiator connect to the target,
> 3. they're using the same physical iscsi disk,
> 4. run LVM2 on top of the same iscsi disk,
> 5. on the same lv (logical volume), I created a gfs2 filesystem,
> 6. mount the gfs2 system to a same path under 2 nodes,
> 7. start samba to shared the gfs2 mounting pointer on the 2 nodes,
>
> now test with windows client, when two or above clients connects to the samba,
> everything is still normal; but when heavy writers or readers start,
> the samba server daemon changed to D state, that's uninterruptible in
> the kernel,
> I wonder that's a problem of gfs2?
>
Which version of gfs2 are you using? GFS2 doesn't support leases which I
know that Samba uses, however only relatively recent kernels have been
able to report that fact via the VFS.
> then I start a simple ls command on the gfs2 mouting point:
> $ ls /mnt/gfs2
> the ls process is also changed to D state,
>
> I think it's problems about readdir implementation in gfs2, and I want
> to fix it, someone could give me some pointers?
>
Can you get a stack trace? echo 't' >/proc/sysrq-trigger
That should show where Samba is getting stuck,
Steve.
WARNING: multiple messages have this Message-ID (diff)
From: Steven Whitehouse <swhiteho@redhat.com>
To: 程任全 <chengrq@uit.com.cn>
Cc: cluster-devel@redhat.com,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [gfs2][RFC] readdir caused ls process into D (uninterruptible) state, under testing with Samba 3.0.25
Date: Thu, 16 Aug 2007 09:28:48 +0100 [thread overview]
Message-ID: <1187252928.8765.881.camel@quoit> (raw)
In-Reply-To: <91b13c310708160120v7379d867k73ecf1995719d694@mail.gmail.com>
Hi,
On Thu, 2007-08-16 at 16:20 +0800, 程任全 wrote:
> It seems that gfs2 cannot work well with Samba,
>
> I'm using the gfs2 and the new cluster suite(cman with openais),
>
> 1. the testing environment is that 1 iscsi target and 2 cluster node,
> 2. the two nodes both used iscsi initiator connect to the target,
> 3. they're using the same physical iscsi disk,
> 4. run LVM2 on top of the same iscsi disk,
> 5. on the same lv (logical volume), I created a gfs2 filesystem,
> 6. mount the gfs2 system to a same path under 2 nodes,
> 7. start samba to shared the gfs2 mounting pointer on the 2 nodes,
>
> now test with windows client, when two or above clients connects to the samba,
> everything is still normal; but when heavy writers or readers start,
> the samba server daemon changed to D state, that's uninterruptible in
> the kernel,
> I wonder that's a problem of gfs2?
>
Which version of gfs2 are you using? GFS2 doesn't support leases which I
know that Samba uses, however only relatively recent kernels have been
able to report that fact via the VFS.
> then I start a simple ls command on the gfs2 mouting point:
> $ ls /mnt/gfs2
> the ls process is also changed to D state,
>
> I think it's problems about readdir implementation in gfs2, and I want
> to fix it, someone could give me some pointers?
>
Can you get a stack trace? echo 't' >/proc/sysrq-trigger
That should show where Samba is getting stuck,
Steve.
next prev parent reply other threads:[~2007-08-16 8:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 8:20 [Cluster-devel] [gfs2][RFC] readdir caused ls process into D (uninterruptible) state, under testing with Samba 3.0.25 程任全
2007-08-16 8:20 ` 程任全
2007-08-16 8:28 ` Steven Whitehouse [this message]
2007-08-16 8:28 ` Steven Whitehouse
2007-08-17 7:43 ` [Cluster-devel] " rae l
2007-08-17 7:43 ` rae l
2007-08-17 15:27 ` Steven Whitehouse
2007-08-17 15:27 ` Steven Whitehouse
2007-08-20 9:36 ` rae l
2007-08-20 9:36 ` rae l
2007-08-20 15:51 ` Steven Whitehouse
2007-08-20 15:51 ` Steven Whitehouse
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=1187252928.8765.881.camel@quoit \
--to=swhiteho@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.