[Ocfs2-devel] [BUG] can not chmod to 777

[Ocfs2-devel] [BUG] can not chmod to 777

[Ling, Xiaofeng]

HI
	I create a directory /ocfs, and take it the mount point of ocfs2
filesystem, but I can not
use "chmod 777" to change its permission, it always shows 755.
Seems this breaks a lot LTP test cases.
I report it as bug 56.

[Ocfs2-devel] [BUG] can not chmod to 777

[Kurt Hackel]

Hi Xiaofeng,

Unfortunately this is the normal behavior of OCFS.  When the filesystem
was originally ported from Windows NT, there was no provision for root
directory permissions (or any other permissions for that matter).  The
only way to change the permissions on the root currently is to use the
tuneocfs tool to change the permissions, uid and/or gid.

If anyone wants to fix this, they would have to make a lock structure
somewhere on the header of the disk (plenty of space there) and
permanently set the OIN_MAP part of the lock structure to all nodes.
Then you would have to handle the release part of that special lock to
understand how to update the root inode when another node changes the
permissions, etc.  Basically need to broadcast the change, and not
continue doing anything locally that depends on the change until you
have gotten a response from all live nodes.


Thanks!
-kurt


On Wed, Apr 14, 2004 at 09:46:30AM +0800, Ling, Xiaofeng wrote:
> HI
> 	I create a directory /ocfs, and take it the mount point of ocfs2
> filesystem, but I can not
> use "chmod 777" to change its permission, it always shows 755.
> Seems this breaks a lot LTP test cases.
> I report it as bug 56.
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel@oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-devel

[Ocfs2-devel] [BUG] can not chmod to 777

[Sunil Mushran]

uhhh... I hope that this is NOT a precursor to dynamic resizing
of the volume too. :-)

Kurt Hackel wrote:

>Hi Xiaofeng,
>
>Unfortunately this is the normal behavior of OCFS.  When the filesystem
>was originally ported from Windows NT, there was no provision for root
>directory permissions (or any other permissions for that matter).  The
>only way to change the permissions on the root currently is to use the
>tuneocfs tool to change the permissions, uid and/or gid.
>
>If anyone wants to fix this, they would have to make a lock structure
>somewhere on the header of the disk (plenty of space there) and
>permanently set the OIN_MAP part of the lock structure to all nodes.
>Then you would have to handle the release part of that special lock to
>understand how to update the root inode when another node changes the
>permissions, etc.  Basically need to broadcast the change, and not
>continue doing anything locally that depends on the change until you
>have gotten a response from all live nodes.
>
>
>Thanks!
>-kurt
>
>
>On Wed, Apr 14, 2004 at 09:46:30AM +0800, Ling, Xiaofeng wrote:
>  
>
>>HI
>>	I create a directory /ocfs, and take it the mount point of ocfs2
>>filesystem, but I can not
>>use "chmod 777" to change its permission, it always shows 755.
>>Seems this breaks a lot LTP test cases.
>>I report it as bug 56.
>>_______________________________________________
>>Ocfs2-devel mailing list
>>Ocfs2-devel@oss.oracle.com
>>http://oss.oracle.com/mailman/listinfo/ocfs2-devel
>>    
>>
>_______________________________________________
>Ocfs2-devel mailing list
>Ocfs2-devel@oss.oracle.com
>http://oss.oracle.com/mailman/listinfo/ocfs2-devel
>  
>

[Ocfs2-devel] [BUG] can not chmod to 777

[Kurt Hackel]

Definitely could be.  Dynamic resizing is not much harder than
dynamically changing the root inode, especially since you have the
advantage of locking out all allocs by taking the global bitmap lock.  
Using the same method, the release lock would be the signal for other
nodes to resize their in-memory bitmaps.  Wouldn't be too difficult.

-k

On Wed, Apr 14, 2004 at 12:12:34PM -0700, Sunil Mushran wrote:
> uhhh... I hope that this is NOT a precursor to dynamic resizing
> of the volume too. :-)
> 
> Kurt Hackel wrote:
> 
> >Hi Xiaofeng,
> >
> >Unfortunately this is the normal behavior of OCFS.  When the filesystem
> >was originally ported from Windows NT, there was no provision for root
> >directory permissions (or any other permissions for that matter).  The
> >only way to change the permissions on the root currently is to use the
> >tuneocfs tool to change the permissions, uid and/or gid.
> >
> >If anyone wants to fix this, they would have to make a lock structure
> >somewhere on the header of the disk (plenty of space there) and
> >permanently set the OIN_MAP part of the lock structure to all nodes.
> >Then you would have to handle the release part of that special lock to
> >understand how to update the root inode when another node changes the
> >permissions, etc.  Basically need to broadcast the change, and not
> >continue doing anything locally that depends on the change until you
> >have gotten a response from all live nodes.
> >
> >
> >Thanks!
> >-kurt
> >
> >
> >On Wed, Apr 14, 2004 at 09:46:30AM +0800, Ling, Xiaofeng wrote:
> > 
> >
> >>HI
> >>	I create a directory /ocfs, and take it the mount point of ocfs2
> >>filesystem, but I can not
> >>use "chmod 777" to change its permission, it always shows 755.
> >>Seems this breaks a lot LTP test cases.
> >>I report it as bug 56.
> >>_______________________________________________
> >>Ocfs2-devel mailing list
> >>Ocfs2-devel@oss.oracle.com
> >>http://oss.oracle.com/mailman/listinfo/ocfs2-devel
> >>   
> >>
> >_______________________________________________
> >Ocfs2-devel mailing list
> >Ocfs2-devel@oss.oracle.com
> >http://oss.oracle.com/mailman/listinfo/ocfs2-devel
> > 
> >
> 
> 

[Ocfs2-devel] [BUG] can not chmod to 777

[Sunil Mushran]

I agree with kurt about adding a lockfe for making changes
in the volhdr. But short of that, if all you are doing is single
node tests, just hack it. As in, comment out the root inode
check in ocfs_setattr and also jump over any code making
fe changes on disk for this. There is no fe for root in ocfs.

This should help in reducing the noise in ltp.

Ling, Xiaofeng wrote:

>HI
>	I create a directory /ocfs, and take it the mount point of ocfs2
>filesystem, but I can not
>use "chmod 777" to change its permission, it always shows 755.
>Seems this breaks a lot LTP test cases.
>I report it as bug 56.
>_______________________________________________
>Ocfs2-devel mailing list
>Ocfs2-devel@oss.oracle.com
>http://oss.oracle.com/mailman/listinfo/ocfs2-devel
>  
>