Project

General

Profile

Actions

Bug #4220

closed

MDS is inconsistent about whether layouts are allowed on the root directory

Added by Greg Farnum about 11 years ago. Updated almost 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
Development
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
MDS
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

I can't seem to set layouts on the root directory with ceph-fuse. Perhaps I'm doing something else wrong, but check out what.

Actions #1

Updated by Greg Farnum about 11 years ago

  • Subject changed from can't set layouts on root directory? to MDS is inconsistent about whether layouts are allowed on the root directory
  • Assignee changed from Greg Farnum to Sage Weil
  • Priority changed from High to Normal

If you go through the "handle_client_setdirlayout" interface (ie, cephfs tool), the MDS will let you set a layout on the root directory. If you go through the "handle_client_setxattr" virtual xattr interface, it won't. There's a special-case check disallowing it and returning EINVAL "//for now".
My suspicion is that we can just unlock this, but perhaps Sage had a reason to think otherwise, in which case we should disallow it through all interfaces.

Actions #2

Updated by Greg Farnum about 11 years ago

  • Category changed from 46 to 47
Actions #3

Updated by Greg Farnum about 11 years ago

  • Status changed from New to Resolved
  • Assignee changed from Sage Weil to Greg Farnum

Right, this is in the generic xattr code, not the new vxattr stuff. Sage says this is because the root inode used to be a construct which was never persisted to disk — but it has been for many years now. So we're just getting rid of that check.

Done in commit:9f82ae60fac30391dfa9d17d2fc014bf9e21f387

Actions #4

Updated by Greg Farnum almost 8 years ago

  • Component(FS) MDS added
Actions

Also available in: Atom PDF