[ceph-users] Re: cephfs - unable to create new subvolume

[Milind Changire]

On Fri, Jul 21, 2023 at 9:03 PM Patrick Donnelly  wrote:
>
> Hello karon,
>
> On Fri, Jun 23, 2023 at 4:55 AM karon karon  wrote:
> >
> > Hello,
> >
> > I recently use cephfs in version 17.2.6
> > I have a pool named "*data*" and a fs "*kube*"
> > it was working fine until a few days ago, now i can no longer create a new
> > subvolume*, *it gives me the following error:
> >
> > Error EINVAL: invalid value specified for ceph.dir.subvolume
>
> We have heard other reports of this. We don't know how, but it seems
> something has erroneously set the subvolume flag on parent
> directories. Please try:
>
> setfattr -n ceph.dir.subvolume -v 0 /volumes/csi
>
> Then check if it works. If still not:
>
> setfattr -n ceph.dir.subvolume -v 0 /volumes/
>
> try again, if still not:
>
> setfattr -n ceph.dir.subvolume -v 0 /
>
> Please let us know which directory fixed the issue for you.

Karon had approached me on Slack #cephfs channel a while earlier, and
has confirmed that these steps have indeed worked for him.

>
> --
> Patrick Donnelly, Ph.D.
> He / Him / His
> Red Hat Partner Engineer
> IBM, Inc.
> GPG: 19F28A586F808C2402351B93C3301A3E258DD79D
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io



-- 
Milind
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: cephfs - unable to create new subvolume

[Patrick Donnelly]

Hello karon,

On Fri, Jun 23, 2023 at 4:55 AM karon karon  wrote:
>
> Hello,
>
> I recently use cephfs in version 17.2.6
> I have a pool named "*data*" and a fs "*kube*"
> it was working fine until a few days ago, now i can no longer create a new
> subvolume*, *it gives me the following error:
>
> Error EINVAL: invalid value specified for ceph.dir.subvolume

We have heard other reports of this. We don't know how, but it seems
something has erroneously set the subvolume flag on parent
directories. Please try:

setfattr -n ceph.dir.subvolume -v 0 /volumes/csi

Then check if it works. If still not:

setfattr -n ceph.dir.subvolume -v 0 /volumes/

try again, if still not:

setfattr -n ceph.dir.subvolume -v 0 /

Please let us know which directory fixed the issue for you.

-- 
Patrick Donnelly, Ph.D.
He / Him / His
Red Hat Partner Engineer
IBM, Inc.
GPG: 19F28A586F808C2402351B93C3301A3E258DD79D
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: cephfs - unable to create new subvolume

[karon karon]

hi
one last clarification: if I create a new FS i can create subvolumes, i
would like to be able to correct the existing FS thank you for your help.


Le ven. 23 juin 2023 à 10:55, karon karon  a écrit :

> Hello,
>
> I recently use cephfs in version 17.2.6
> I have a pool named "*data*" and a fs "*kube*"
> it was working fine until a few days ago, now i can no longer create a new
> subvolume*, *it gives me the following error:
>
> Error EINVAL: invalid value specified for ceph.dir.subvolume
>>
>
> here is the command used:
>
> ceph fs subvolume create kube newcsivol --pool_layout data
>>
>
> from what I understand it seems that it creates the subvolume but
> immediately puts it in the trash !? here is the log :
>
> 2023-06-23T08:30:53.307+ 7f2b929d2700  0 log_channel(audit) log [DBG]
>> : from='client.86289 -' entity='client.admin' cmd=[{"prefix": "fs subvolume
>> create", "vol_name": "kube", "sub_name": "newcsivol", "group_name": "csi",
>> "pool_layout": "data", "target": ["mon-mgr", ""]}]: dispatch
>> 2023-06-23T08:30:53.307+ 7f2b8a1d1700  0 [volumes INFO
>> volumes.module] Starting _cmd_fs_subvolume_create(group_name:csi,
>> pool_layout:data, prefix:fs subvolume create, sub_name:newcsivol,
>> target:['mon-mgr', ''], vol_name:kube) < ""
>> 2023-06-23T08:30:53.327+ 7f2b8a1d1700  0 [volumes INFO
>> volumes.fs.operations.versions.subvolume_v2] cleaning up subvolume with
>> path: newcsivol
>> 2023-06-23T08:30:53.331+ 7f2b8a1d1700  0 [volumes INFO
>> volumes.fs.operations.versions.subvolume_base] subvolume path
>> 'b'/volumes/csi/newcsivol'' moved to trashcan
>> 2023-06-23T08:30:53.331+ 7f2b8a1d1700  0 [volumes INFO
>> volumes.fs.async_job] queuing job for volume 'kube'
>> 2023-06-23T08:30:53.335+ 7f2b8a1d1700  0 [volumes INFO
>> volumes.module] Finishing _cmd_fs_subvolume_create(group_name:csi,
>> pool_layout:data, prefix:fs subvolume create, sub_name:newcsivol,
>> target:['mon-mgr', ''], vol_name:kube) < ""
>> 2023-06-23T08:30:53.335+ 7f2b8a1d1700 -1 mgr.server reply reply (22)
>> Invalid argument invalid value specified for ceph.dir.subvolume
>> 2023-06-23T08:30:53.339+ 7f2b461bf700 -1 client.0 error registering
>> admin socket command: (17) File exists
>> 2023-06-23T08:30:53.339+ 7f2b461bf700 -1 client.0 error registering
>> admin socket command: (17) File exists
>> 2023-06-23T08:30:53.339+ 7f2b461bf700 -1 client.0 error registering
>> admin socket command: (17) File exists
>> 2023-06-23T08:30:53.339+ 7f2b461bf700 -1 client.0 error registering
>> admin socket command: (17) File exists
>> 2023-06-23T08:30:53.339+ 7f2b461bf700 -1 client.0 error registering
>> admin socket command: (17) File exists
>> 2023-06-23T08:30:53.363+ 7f2b461bf700 -1 client.0 error registering
>> admin socket command: (17) File exists
>> 2023-06-23T08:30:53.363+ 7f2b461bf700 -1 client.0 error registering
>> admin socket command: (17) File exists
>> 2023-06-23T08:30:53.363+ 7f2b461bf700 -1 client.0 error registering
>> admin socket command: (17) File exists
>> 2023-06-23T08:30:53.363+ 7f2b461bf700 -1 client.0 error registering
>> admin socket command: (17) File exists
>> 2023-06-23T08:30:53.363+ 7f2b461bf700 -1 client.0 error registering
>> admin socket command: (17) File exists
>> 2023-06-23T08:30:53.383+ 7f2b479c2700 -1 client.0 error registering
>> admin socket command: (17) File exists
>> 2023-06-23T08:30:53.383+ 7f2b479c2700 -1 client.0 error registering
>> admin socket command: (17) File exists
>> 2023-06-23T08:30:53.383+ 7f2b479c2700 -1 client.0 error registering
>> admin socket command: (17) File exists
>> 2023-06-23T08:30:53.383+ 7f2b479c2700 -1 client.0 error registering
>> admin socket command: (17) File exists
>> 2023-06-23T08:30:53.383+ 7f2b479c2700 -1 client.0 error registering
>> admin socket command: (17) File exists
>> 2023-06-23T08:30:53.507+ 7f2b3ff33700  0 [prometheus INFO
>> cherrypy.access.139824530773776] 192.168.240.231 - - [23/Jun/2023:08:30:53]
>> "GET /metrics HTTP/1.1" 200 194558 "" "Prometheus/2.33.4"
>> 2023-06-23T08:30:54.219+ 7f2b3ddaf700  0 [dashboard INFO request] [
>> 172.29.2.142:33040] [GET] [200] [0.003s] [admin] [22.0B]
>> /api/prometheus/notifications
>> 2023-06-23T08:30:54.223+ 7f2b929d2700  0 log_channel(audit) log [DBG]
>> : from='mon.0 -' entity='mon.' cmd=[{"prefix": "balancer status", "format":
>> "json"}]: dispatch
>> 2023-06-23T08:30:54.227+ 7f2b3a5a8700  0 [dashboard INFO request] [
>> 172.29.2.142:49348] [GET] [200] [0.019s] [admin] [22.0B] /api/prometheus
>> 2023-06-23T08:30:54.227+ 7f2b929d2700  0 log_channel(audit) log [DBG]
>> : from='mon.0 -' entity='mon.' cmd=[{"prefix": "balancer status", "format":
>> "json"}]: dispatch
>> 2023-06-23T08:30:54.231+ 7f2b3d5ae700  0 [dashboard INFO request] [
>> 172.29.2.142:39414] [GET] [200] [0.022s] [admin] [9.3K]
>> /api/prometheus/rules
>> 2023-06-23T08:30:54.275+ 7f2ba39d4700  0 log_channel(cluster) log
>> [DBG] : pgmap