[Ocfs2-tools-devel] [PATCH] Option to skip cluster checking in tunefs.ocfs2

[Lars Marowsky-Bree]

On 2009-10-20T14:01:16, Joel Becker <Joel.Becker at oracle.com> wrote:

> > I don't get the resistance to being able to force this if the stack is
> > down. (We have so many ways how root can screw up a Linux system.) I
> > could just get out a hex editor and do as I please, anyway ;-) 
> 	Allowing root to play with fire is fine.  But why hand out
> matches if there is already a perfectly good pizo-electric starter?

Because they burn so nicely. (You're talking to a pyromaniac, sorry. I
had a fire truck come screaming once, just because I was playing with my
fire bowl.)

> > Some admins may prefer to make changes to an OCFS2 mount in a
> > virtualized environment too (ie, modifying the fs on Dom0 while the
> > DomUs are stopped).
> 	*This* is a logical use case that requires some thought.  Of
> course, you could just bring up a domU.

Not as easily scripted. The point is that there tend to be valid use
cases for force options from time to time, and that it can be a nuisance
when they aren't around. Maybe I just don't like my system to boss me
around ;-)

> 	Years of experience is that most people always run with --force.
> Then they call support.

I get that quite frequently. On the other hand, we do want them to have
reasons to sign support contracts ...

> > # tunefs.ocfs2 -v --fs-features xattr /dev/dm-6
> > Enabling feature "xattr"
> > Cannot lock the filesystem. If you are sure the filesystem is not
> > mounted on any node, you can use --force or -F to skip this check.
> > tunefs.ocfs2: Unable to access cluster service while opening device "/dev/dm-6"
> > 
> > That _is_ with the stack up and the fs umounted. (And, admittedly, with
> > Jan's patch.)
> 
> 	I wonder what is going on there.  Do you have the filesystem
> mounted on other nodes?  (I figured it had Jan's patch)

Not mounted anywhere, lock space not present on any node.

> > dlm_tool ls does not show the lockspace, yet I seem to be hitting this
> > problem. Or is this another issue?
> 	Weird.  I wonder what's up there.  Can you strace the sucker,
> see where the error is?

Right. I think I win a brown-paper bag, this doesn't look like the LVB
issue at all, but probably a build issue I don't understand quite yet -
looks as if tunefs.ocfs2 is looking for, but not finding, some plugin.

I attached the strace and will go looking at the code for a bit now ;-)


Regards,
    Lars

-- 
Architect Storage/HA, OPS Engineering, Novell, Inc.
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde

-------------- next part --------------
A non-text attachment was scrubbed...
Name: tunefs.ocfs2.strace.bz2
Type: application/x-bzip
Size: 3302 bytes
Desc: not available
Url : http://oss.oracle.com/pipermail/ocfs2-tools-devel/attachments/20091020/b74a4f60/attachment.bin