Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 78091 - gid bit on directories does not work in tmpfs
Summary: gid bit on directories does not work in tmpfs
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 8.0
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2002-11-18 23:16 UTC by Kevin J. Miller
Modified: 2008-08-01 16:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2004-09-30 15:40:12 UTC

Attachments (Terms of Use)

Description Kevin J. Miller 2002-11-18 23:16:51 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
If I have a directory in a tmpfs partition, and the gid bit is set, files
created in this directory will still have the user's default group rather than
the group of the directory.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. mkdir /mnt/tmpfs/some_dir
2. chgrp other_group /mnt/tmpfs/some_dir
3. chmod g+s /mnt/tmpfs/some_dir
4. touch /mnt/tmpfs/some_dir/a_file
5. ls -l /mnt/tmpfs/some_dir/a_file

Actual Results:  The /mnt/tmpfs/some_dir/a_file is owned by my_group.

Expected Results:  The /mnt/tmpfs/some_dir/a_file should be owned by other_group.

Additional info:

Comment 1 Bugzilla owner 2004-09-30 15:40:12 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem

The Fedora Legacy project ( maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at:

Note You need to log in before you can comment on or make changes to this bug.