Skip to contentSkip to conversation

chmod errors compiling on btrfs

DISCUSSION Andrew Benton 2 participants 5 messages Nov 7, 2009 – Nov 9, 2009 Btrfs file system

lore
Share & tools
lore
#0 lore raw

Hello World.
I've created a btrfs partition and have tried compiling some programs on it, however, some of them fail with errors due to incorrect permissions. e2fsprogs fails like this:-

make[1]: Leaving directory /mnt/btrfs/sources/e2fsprogs-1.41.9' make[1]: Entering directory /mnt/btrfs/sources/e2fsprogs-1.41.9/lib/et'
SUBST compile_et
make[1]: Leaving directory /mnt/btrfs/sources/e2fsprogs-1.41.9/lib/et' make[1]: Entering directory /mnt/btrfs/sources/e2fsprogs-1.41.9/lib/ext2fs'
SUBST ext2_err.et
COMPILE_ET ext2_err.et
chmod: ext2_err.h: new permissions are r--r--rw-, not r--r--r--
chmod: ext2_err.c: new permissions are r--r--rw-, not r--r--r-- make[1]: *** [ext2_err.h] Error 1
make[1]: Leaving directory `/mnt/btrfs/sources/e2fsprogs-1.41.9/lib/ext2fs'
make: *** [subs] Error 2 andy:/mnt/btrfs/sources/e2fsprogs-1.41.9$

and coreutils fails like this:-

  CCLD   hostname
  CCLD   setuidgid
  CCLD   getlimits
  CCLD   su

make[3]: Leaving directory /mnt/btrfs/sources/coreutils-7.6/src' make[2]: Leaving directory /mnt/btrfs/sources/coreutils-7.6/src' Making all in doc
make[2]: Entering directory /mnt/btrfs/sources/coreutils-7.6/doc' make[2]: Nothing to be done for all'.
make[2]: Leaving directory `/mnt/btrfs/sources/coreutils-7.6/doc' Making all in man
make[2]: Entering directory `/mnt/btrfs/sources/coreutils-7.6/man'
GEN hostname.1
chmod: hostname.1-t: new permissions are r--rw-rw-, not r--r--r-- make[2]: *** [hostname.1] Error 1
make[2]: Leaving directory `/mnt/btrfs/sources/coreutils-7.6/man' make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/mnt/btrfs/sources/coreutils-7.6'
make: *** [all] Error 2
andy:/mnt/btrfs/sources$

Both times the files created were world writeable when they should have been read only. I get the same errors if I compile as myself or root. If I compile in my home folder (on a reiserfs partition) they compile with no problem. I'm using a self compiled vanila 2.6.31.4 kernel. I created the partition with btrfs-progs-0.19.

Andy
(Andrew Benton)

#1 lore raw
Quoted 6 lines · Andrew Benton

Both times the files created were world writeable when they should have been read only. I get the same errors if I compile as myself or root. If I compile in my home folder (on a reiserfs partition) they compile with no problem. I'm using a self compiled vanila 2.6.31.4 kernel. I created the partition with btrfs-progs-0.19.

We fixed some umask problems recently, these should be fixed in the master branch of the btrfs-unstable repo (which is against 2.6.31).

-chris

#2 lore raw
Quoted 11 lines · Chris Mason
Quoted 6 lines · Andrew Benton

Both times the files created were world writeable when they should have been read only. I get the same errors if I compile as myself or root. If I compile in my home folder (on a reiserfs partition) they compile with no problem. I'm using a self compiled vanila 2.6.31.4 kernel. I created the partition with btrfs-progs-0.19.

We fixed some umask problems recently, these should be fixed in the master branch of the btrfs-unstable repo (which is against 2.6.31).

Thanks, I'll give that a try

Andy

#3 lore raw
In reply to Chris Mason
Quoted 3 lines · Chris Mason

We fixed some umask problems recently, these should be fixed in the master branch of the btrfs-unstable repo (which is against 2.6.31).

Thanks, that did the trick. Will these umask fixes be in the 2.6.32 kernel?

Andy

#4 lore raw
Quoted 6 lines · Andrew Benton
Quoted 3 lines · Chris Mason

We fixed some umask problems recently, these should be fixed in the master branch of the btrfs-unstable repo (which is against 2.6.31).

Thanks, that did the trick. Will these umask fixes be in the 2.6.32 kernel?

Great. They are already included in 2.6.32-rc releases

-chris