[Linux-cluster] "gfs_mkfs -p LockProtoName" problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "linux-cluster@xxxxxxxxxx" <linux-cluster@xxxxxxxxxx>
Subject: [Linux-cluster] "gfs_mkfs -p LockProtoName" problem
From: "孙俊伟" <sunjw@xxxxxxxxxxxxxx>
Date: Mon, 18 Oct 2004 17:54:03 +0800
Reply-to: Discussion of clustering software components including GFS <linux-cluster@xxxxxxxxxx>

Hello,all.
	How can I use the LockProtoName: lock_gulm,lock_nolock?
When I use lock_gulm to make gfs filesystem,I can not mount the filesystem.
When lock_nolock, the gfs can be mounted,but when writed, the kernel paniced.
Is that true that I can only use lock_dlm in GFS 6.1pre2 + kernel 2.6.8.1 ?

Thanks for any reply!
			
Best regards!

Luckey Sun

Follow-Ups:
- Re: [Linux-cluster] "gfs_mkfs -p LockProtoName" problem
  - From: Adam Manthei

Prev by Date: 答复: [Linux-cluster] Compile problem under Fedora Core2 2.6.5-1.358
Next by Date: Re: [Linux-cluster] Discover persistent/orphan lock
Previous by thread: [Linux-cluster] EAGAIN from dlm_lock: bug or feature?
Next by thread: Re: [Linux-cluster] "gfs_mkfs -p LockProtoName" problem
Index(es):
- Date
- Thread

[Index of Archives] [Corosync Cluster Engine] [GFS] [Linux Virtualization] [Centos Virtualization] [Centos] [Linux RAID] [Fedora Users] [Fedora SELinux] [Big List of Linux Books] [Yosemite Camping]

Powered by Linux