Re: Unintuitive (buggy?) CephFS behaviour when dealing with pool_namespace layout attribute

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 06/03/2025 09:46, Florian Haas wrote:
On 05/03/2025 20:45, Frédéric Nass wrote:
Hi Florian,

Point 1 is certainly a bug regarding the choice of terms in the response
(confusion between file and directory).

Well... no, I don't think so. Rather, I'd guess it's simply a result of
setfattr returning ENOTEMPTY (errno 39), which the shell then renders as
"Directory not empty".

Perhaps setting the ceph.file.layout attribute on an empty file should
really result in EPERM (errno 1) though. Or maybe even EFBIG (errno 27,
"File too large), because the operation is only supported on a file that
is 0 bytes in length, and fails on any file larger than that.

Sorry, confusing error. I meant to posit, of course, that setting the ceph.file.layout attribute on a *non*-empty file should result in EPERM or EFBIG, rather than ENOTEMPTY. Apologies.

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx

[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux