linux-kernel - [gfs2][RFC] readdir caused ls process into D (uninterruptible) state, under testing with Samba 3.0.25

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <91b13c310708160120v7379d867k73ecf1995719d694@mail.gmail.com>
Date:	Thu, 16 Aug 2007 16:20:11 +0800
From:	"程任全" <chengrq@....com.cn>
To:	cluster-devel@...hat.com
Cc:	"Steven Whitehouse" <swhiteho@...hat.com>,
	"Linux Kernel list" <linux-kernel@...r.kernel.org>
Subject: [gfs2][RFC] readdir caused ls process into D (uninterruptible) state, under testing with Samba 3.0.25

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?

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?

-- 
Denis Cheng
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/