On Fri, Dec 05, 2008 at 09:51:45AM +, Steven Whitehouse wrote:
In that case gfs2 should be able to generate the id itself from the
fsname and it still doesn't need it passed in, even if it continues to
expose the id in sysfs.
Perhaps better still, it should be possible for David to
On Fri, Dec 05, 2008 at 08:52:58AM -0600, David Teigland wrote:
On Fri, Dec 05, 2008 at 09:51:45AM +, Steven Whitehouse wrote:
In that case gfs2 should be able to generate the id itself from the
fsname and it still doesn't need it passed in, even if it continues to
expose the id in
On Thu, Dec 4, 2008 at 5:38 PM, David Teigland [EMAIL PROTECTED] wrote:
On Thu, Dec 04, 2008 at 04:59:23PM -0500, david m. richter wrote:
ah, so just to make sure i'm with you here: (1) gfs_controld is
generating this id-which-is-the-mountgroup-id, and (2) gfs_kernel
will no longer receive
On Mon, Dec 1, 2008 at 12:31 PM, David Teigland [EMAIL PROTECTED] wrote:
Here are the compatibility aspects to the recent ideas about changes to
the user/kernel interface between gfs (1 2) and gfs_controld.
. gfs_controld can remove id from hostdata string in mount options
hi david,
I know
On Thu, Dec 04, 2008 at 01:32:31PM -0500, david m. richter wrote:
On Mon, Dec 1, 2008 at 12:31 PM, David Teigland [EMAIL PROTECTED] wrote:
Here are the compatibility aspects to the recent ideas about changes to
the user/kernel interface between gfs (1 2) and gfs_controld.
. gfs_controld
On Thu, Dec 4, 2008 at 4:07 PM, David Teigland [EMAIL PROTECTED] wrote:
On Thu, Dec 04, 2008 at 01:32:31PM -0500, david m. richter wrote:
On Mon, Dec 1, 2008 at 12:31 PM, David Teigland [EMAIL PROTECTED] wrote:
Here are the compatibility aspects to the recent ideas about changes to
the
Here are the compatibility aspects to the recent ideas about changes to
the user/kernel interface between gfs (1 2) and gfs_controld.
. gfs_controld can remove id from hostdata string in mount options
- no compat issues AFAICT
. getting rid of id sysfs file from lock_dlm
- new
