[LU-7093] mkdir: cannot create directory: Operation not permitted

• Type: Bug
• Resolution: Fixed
• Priority: Critical
• Fix Version/s: Lustre 2.8.0
• Affects Version/s: Lustre 2.8.0
• Labels: dne llnl zfs
• Environment: lustre-2.7.57-2.6.32_504.16.2.1chaos.ch5.3.x86_64_gea38322.x86_64; Redhat 2.6.32-504.16.2.1chaos.ch5.3.x86_64
• Severity: 3
• Assignee: Di Wang
• Reporter: Giuseppe Di Natale (Inactive)

Description

In a a set of directories on ldne, /p/ldne/dinatale/count4_index*, Joe is able to create a file, but not a directory. Joe owns the directories and the mode is set to 700.

In other directories, for example /p/ldne/dinatale/count3_index*, Joe is able to create both files and directories successfully. They have the same ownership and mode.

zwicky96@dinatale:pwd
/p/ldne/dinatale/count4_index0

zwicky96@dinatale:ls -al
total 54
drwx------  2 dinatale lcstaff 43008 Sep  1 14:13 .
dr-xr-xr-x 18 dinatale lcstaff 11776 Aug 31 11:32 ..

zwicky96@dinatale:date > something

zwicky96@dinatale:ls -l something
-rw------- 1 dinatale dinatale 29 Sep  1 15:45 something

zwicky96@dinatale:rm something

zwicky96@dinatale:ls -al                                                                          
total 54
drwx------  2 dinatale lcstaff 43008 Sep  1 15:46 .
dr-xr-xr-x 18 dinatale lcstaff 11776 Aug 31 11:32 ..

zwicky96@dinatale:mkdir something
mkdir: cannot create directory `something': Operation not permitted

zwicky96@dinatale:ls -al            
total 54
drwx------  2 dinatale lcstaff 43008 Sep  1 15:46 .
dr-xr-xr-x 18 dinatale lcstaff 11776 Aug 31 11:32 ..

zwicky96@dinatale:rpm -q lustre
lustre-2.7.57-2.6.32_504.16.2.1chaos.ch5.3.x86_64_gea38322.x86_64

zwicky96@dinatale:distro_version
toss 2.3-6.ch5.3

zwicky96@dinatale:lfs getdirstripe .
.
lmv_stripe_count: 4 lmv_stripe_offset: 0
mdtidx           FID[seq:oid:ver]
     0           [0x200000453:0x1ff:0x0]
     1           [0x280000411:0x1ff:0x0]
     2           [0x24000041c:0x1fe:0x0]
     3           [0x2c000040b:0x1fd:0x0]

zwicky96@dinatale:pwd
/p/ldne/dinatale/count4_index0

zwicky96@dinatale:ls -ld ../count4_index*
drwx------ 2 dinatale lcstaff 43008 Sep  1 15:46 ../count4_index0
drwx------ 2 dinatale lcstaff 43008 Sep  1 14:00 ../count4_index1
drwx------ 2 dinatale lcstaff 43008 Sep  1 14:00 ../count4_index2
drwx------ 2 dinatale lcstaff 43008 Sep  1 14:00 ../count4_index3

zwicky96@dinatale:ls -ld ../count3_index*
drwx------ 3 dinatale lcstaff 32256 Sep  1 14:06 ../count3_index0
drwx------ 3 dinatale lcstaff 32256 Sep  1 14:06 ../count3_index1
drwx------ 3 dinatale lcstaff 32256 Sep  1 14:06 ../count3_index2
drwx------ 3 dinatale lcstaff 32256 Sep  1 14:06 ../count3_index3

We are running 4 MDSs each w/ 1 MDT, 2 OSSs each w/ 1 OST, and clients are running the same lustre version as the servers. Backend is zfs.

Issue Links

• is related to: LU-6341 Do not check security when accessing default stripeEA
• is related to: LU-7013 replay-single test_110c: FAIL: create striped dir failed

Comments

[Joseph Gmitter (Inactive)]

Landed for 2.8.

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch http://review.whamcloud.com/16286/
Subject: LU-7093 mdt: Remote operation permission check
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 703195acc2157969e66cb07946522b918dfd7dea

[Gerrit Updater]

wangdi ([e-mail]) uploaded a new patch: http://review.whamcloud.com/16286
Subject: LU-7093 mdt: Remote operation permission check
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 482a09045f2d8be0681146c01c7c7a248ed0f559

[Andreas Dilger]

I think the check needs to be that if a striped directory exists, the users can create subdirectories under the striped directory regardless of the extra /proc setting. Also, setting the default directory striping itself needs to check the extra /proc setting, but once it is set then the regular user can create subdirectories according to this policy.

[Di Wang]

I still find it odd that a user may be allowed to make a striped directory even though they are not allowed to actually create remote directories. 

hmm, this maybe a problem. I will work on a fix, thanks for finding this.

[Giuseppe Di Natale (Inactive)]

Di, thank you for the explanation. It makes sense now.

I still find it odd that a user may be allowed to make a striped directory even though they are not allowed to actually create remote directories. Wouldn't it be better behavior to not permit users to make striped directories if remote directories is disabled? Likewise, if remote directories are enabled and a striped directory exists in the filesystem, then remote directories cannot be disabled?